Hi @swartzfeger,

Could you please check joins used in th GI?

I belive you have used INSite table more than once in table relations in GI.

Sorry Dipak, I’m not a SQL guy but this is what I found --

Hi @swartzfeger,

Could you please check joins used in th GI?

I belive you have used INSite table more than once in table relations in GI.

 

Sorry Dipak, I’m not a SQL guy but this is what I found --

 

 

@swartzfeger You should be able to remove one of the rows where the “Child Table” is set to “INSite” and it will work! Looking at the XML file you provided, both relations will join based on the SiteID field from both tables. If you keep the row with the “Inner” join type, it will only return results where the Work Center’s site ID is matched an INSite. If you keep the row with the “Left” join type, it will return all Work Centers even if they don’t match with an INSite, and these Work Center returned from the query will then be used in the other joins listed here. What you decide to use will depend on the purpose of the GI.

Hi @swartzfeger,

Could you please check joins used in th GI?

I belive you have used INSite table more than once in table relations in GI.

 

Sorry Dipak, I’m not a SQL guy but this is what I found --

 

 

@swartzfeger You should be able to remove one of the rows where the “Child Table” is set to “INSite” and it will work! Looking at the XML file you provided, both relations will join based on the SiteID field from both tables. If you keep the row with the “Inner” join type, it will only return results where the Work Center’s site ID is matched an INSite. If you keep the row with the “Left” join type, it will return all Work Centers even if they don’t match with an INSite, and these Work Center returned from the query will then be used in the other joins listed here. What you decide to use will depend on the purpose of the GI.

Nicholas, thank you sir -- that did the trick! Thank you for the help, it’s appreciated!