Quick Update. I think I must’ve done something wrong but the new Error states this: 

The multi-part identifier "Contract.ContractCD" could not be bound. The multi-part identifier "Contract.ContractCD" could not be bound.

@krausef77  In most cases this error means you have bad table relations. Contract Table has ContractID as the key and it should be added to relations in case the Contract table Data needs to be retrieved.

You can share your GI xml file so we can take a closer look if issue not resolved.

@krausef77 one thing that i can see from your screen shots is that you used left join for your inventory subaccount segment and you are using inner for the project one.  maybe change that to left?  it will be helpful to have the file as well so if that doesn’t work, please share

thanks!

Hello,

Are you able to include the entire ContractCD in one column of your GI, then use a calculated column “Segment 1” in another column of the GI to obtain the contract ID segment you need?  For example LEFT(LContract.ContractCD],3), and then Group by and aggregate based on the calculated field “Segment 1”?

Hi there,

It’s a small thing, but you may want to try SegmentID = ‘1’, with the quotes.  That’s what I’ve had to do when doing joins at the Segment-level.

When we do table joins the CD generally is a substitute key for the ID of the DAC, therefore it should be ContractID_Segment1 if it exists that is. If it doesn’t exist, then I would just use Substring function to calculate it. 

Here’s an example if the we want to start from position 0 (starting position) with a length of 3. That should resolve your issue. 

=Substring(SPMProject.ContractCD],0,3)