Skip to main content
Solved

Error: Multi part identifier could not be bound

  • 24 July 2024
  • 6 replies
  • 96 views

Hello all,

I have been working on a GI where I am referencing a sub-GI. But whenever I apply any filter it throws me the following error:
 

How to resolve this?

Hi @Harry 

Please send the xml file of this GI so we can find out the cause of the error.

 

Best Regards,

NNT

Hi @Harry 

Please send the xml file of this GI so we can find out the cause of the error.

 

Best Regards,

NNT

Attached are the files.

Hi @Harry 

I tested on the version_2024R1_24.107.0004 and found no errors.

 

 

 

Best Regards,

NNT

Hi @Harry 

I tested on the version_2024R1_24.107.0004 and found no errors.

 

 

 

Best Regards,

NNT

Hey @nhatnghetinh ,
its just when I filter some value → click OK and then click on any of the column names then the error gets triggered.

Hi @Harry ,

This might be caused by specific data, as I've tried it in the 24 R1 sales demo instance. After applying filters, the GI is working fine and I'm not encountering any errors.

I am getting the error The multi-part identifier "PMQuote.QuoteID" could not be bound.

Relationship CROpportunityProducts Inner join PMQuote

Link CROpportunityProducts.QuoteID Equals PMQuote.QuoteID

This worked well on version prior to upgrade to 2024R1.

How can this be resolved On the DAC the QuoteID  is visible on both tables

Reply


Terms & ConditionsCookie settings