web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Adding Custom View to Form Data Source causes CROSS JOIN and duplicate rows

(0) ShareShare
ReportReport
Posted on by

Hi,

I'm having problems adding a data source to the EcoResProductDetails form. When I add my custom view to the Data Sources, set the JoinSource to be "EcoResProduct" and LinkType to "OuterJoin" I am getting duplicate rows and SQL Trace is showing me that the generated SQL has a CROSS JOIN to my table, hence the duplicates.

My view is returning one row per Product (Product RecId, Attribute1, Attribute2).

Is there something missing in my View definition (or underlying Query) that prevents AX from knowing which field to use to join my view to EcoResProduct? 

SELECT T1.PRODUCTMASTER,T1.RETAITOTALWEIGHT,T1.VARIANTCONFIGURATIONTECHNOLOGY,T1.RETAILCOLORGROUPID,T1.RETAILSIZEGROUPID,T1.RETAILSTYLEGROUPID,T1.INSTANCERELATIONTYPE,T1.DISPLAYPRODUCTNUMBER,T1.SEARCHNAME,T1.PRODUCTTYPE,T1.PDSCWPRODUCT,T1.MODIFIEDBY,T1.RECVERSION,T1.RELATIONTYPE,T1.PARTITION,T1.RECID,T2.PRODUCTDIMENSIONGROUP,T2.PRODUCT,T2.MODIFIEDBY,T2.RECVERSION,T2.PARTITION,T2.RECID,T3.PRODUCTMASTER,T3.ISVARIANTGENERATIONENABLED,T3.ISREUSECONFIGURATIONENABLED,T3.RECVERSION,T3.PARTITION,T3.RECID,T4.PRODUCT,T4.STORAGEDIMENSIONGROUP,T4.RECVERSION,T4.PARTITION,T4.RECID,T5.PRODUCT,T5.TRACKINGDIMENSIONGROUP,T5.RECVERSION,T5.PARTITION,T5.RECID,T6.DESCRIPTION,T6.NAME,T6.PRODUCT,T6.LANGUAGEID,T6.MODIFIEDBY,T6.RECVERSION,T6.PARTITION,T6.RECID,T7.HARMONIZEDCODE,T7.NMFCCODE,T7.PRODUCT,T7.STCCCODE,T7.RECVERSION,T7.PARTITION,T7.RECID,T8.OEM,T8.PRODUCTRANGE,T8.PARTITION,T8.RECID,T9.NAME,T9.RECVERSION,T9.RECID 
FROM  ECORESPRODUCT T1 
LEFT OUTER JOIN ECORESPRODUCTDIMENSIONGROUPPRODUCT T2 ON ((T2.PARTITION=@P1) AND (T1.RECID=T2.PRODUCT)) 
LEFT OUTER JOIN ECORESPRODUCTMASTERMODELINGPOLICY T3 ON ((T3.PARTITION=@P2) AND (T1.RECID=T3.PRODUCTMASTER)) 
LEFT OUTER JOIN ECORESSTORAGEDIMENSIONGROUPPRODUCT T4 ON ((T4.PARTITION=@P3) AND (T1.RECID=T4.PRODUCT)) 
LEFT OUTER JOIN ECORESTRACKINGDIMENSIONGROUPPRODUCT T5 ON ((T5.PARTITION=@P4) AND (T1.RECID=T5.PRODUCT)) 
LEFT OUTER JOIN ECORESPRODUCTTRANSLATION T6 ON ((T6.PARTITION=@P5) AND ((T6.LANGUAGEID=@P6) AND (T1.RECID=T6.PRODUCT))) 
LEFT OUTER JOIN WHSECORESPRODUCTTRANSPORTATIONCODES T7 ON ((T7.PARTITION=@P7) AND (T1.RECID=T7.PRODUCT)) 
CROSS JOIN HYDPRODUCTATTRIBUTEVALUEVIEW T8 
LEFT OUTER JOIN ECORESPRODUCTDIMENSIONGROUP T9 ON ((T9.PARTITION=@P8) AND (T2.PRODUCTDIMENSIONGROUP=T9.RECID)) 
WHERE ((T1.PARTITION=@P9) AND ((T1.INSTANCERELATIONTYPE=@P10) OR (T1.INSTANCERELATIONTYPE=@P11))) 
AND ((((((T8.PARTITION=@P12) AND ((T8.PARTITION#2=@P13) OR (T8.PARTITION#2 IS NULL))) AND ((T8.PARTITION#3=@P14) OR (T8.PARTITION#3 IS NULL))) AND ((T8.PARTITION#4=@P15) OR (T8.PARTITION#4 IS NULL))) AND ((T8.PARTITION#5=@P16) OR (T8.PARTITION#5 IS NULL))) AND ((T8.PARTITION#6=@P17) OR (T8.PARTITION#6 IS NULL))) AND EXISTS (SELECT 'x' FROM ECORESPRODUCTCATEGORY T10 WHERE ((T10.PARTITION=@P18) AND ((T10.CATEGORYHIERARCHY=@P19) AND (T10.PRODUCT=T1.RECID)))) ORDER BY T1.DISPLAYPRODUCTNUMBER OPTION(FAST 4)



SELECT T1.PRODUCTMASTER,T1.RETAITOTALWEIGHT,T1.VARIANTCONFIGURATIONTECHNOLOGY,T1.RETAILCOLORGROUPID,T1.RETAILSIZEGROUPID,T1.RETAILSTYLEGROUPID,T1.INSTANCERELATIONTYPE,T1.DISPLAYPRODUCTNUMBER,T1.SEARCHNAME,T1.PRODUCTTYPE,T1.PDSCWPRODUCT,T1.MODIFIEDBY,T1.RECVERSION,T1.RELATIONTYPE,T1.PARTITION,T1.RECID,T2.PRODUCTDIMENSIONGROUP,T2.PRODUCT,T2.MODIFIEDBY,T2.RECVERSION,T2.PARTITION,T2.RECID,T3.PRODUCTMASTER,T3.ISVARIANTGENERATIONENABLED,T3.ISREUSECONFIGURATIONENABLED,T3.RECVERSION,T3.PARTITION,T3.RECID,T4.PRODUCT,T4.STORAGEDIMENSIONGROUP,T4.RECVERSION,T4.PARTITION,T4.RECID,T5.PRODUCT,T5.TRACKINGDIMENSIONGROUP,T5.RECVERSION,T5.PARTITION,T5.RECID,T6.DESCRIPTION,T6.NAME,T6.PRODUCT,T6.LANGUAGEID,T6.MODIFIEDBY,T6.RECVERSION,T6.PARTITION,T6.RECID,T7.HARMONIZEDCODE,T7.NMFCCODE,T7.PRODUCT,T7.STCCCODE,T7.RECVERSION,T7.PARTITION,T7.RECID,T8.OEM,T8.PRODUCTRANGE,T8.PARTITION,T8.RECID,T9.NAME,T9.RECVERSION,T9.RECID FROM  ECORESPRODUCT T1 LEFT OUTER JOIN ECORESPRODUCTDIMENSIONGROUPPRODUCT T2 ON ((T2.PARTITION=@P1) AND (T1.RECID=T2.PRODUCT)) LEFT OUTER JOIN ECORESPRODUCTMASTERMODELINGPOLICY T3 ON ((T3.PARTITION=@P2) AND (T1.RECID=T3.PRODUCTMASTER)) LEFT OUTER JOIN ECORESSTORAGEDIMENSIONGROUPPRODUCT T4 ON ((T4.PARTITION=@P3) AND (T1.RECID=T4.PRODUCT)) LEFT OUTER JOIN ECORESTRACKINGDIMENSIONGROUPPRODUCT T5 ON ((T5.PARTITION=@P4) AND (T1.RECID=T5.PRODUCT)) LEFT OUTER JOIN ECORESPRODUCTTRANSLATION T6 ON ((T6.PARTITION=@P5) AND ((T6.LANGUAGEID=@P6) AND (T1.RECID=T6.PRODUCT))) LEFT OUTER JOIN WHSECORESPRODUCTTRANSPORTATIONCODES T7 ON ((T7.PARTITION=@P7) AND (T1.RECID=T7.PRODUCT)) CROSS JOIN HYDPRODUCTATTRIBUTEVALUEVIEW T8 LEFT OUTER JOIN ECORESPRODUCTDIMENSIONGROUP T9 ON ((T9.PARTITION=@P8) AND (T2.PRODUCTDIMENSIONGROUP=T9.RECID)) WHERE ((T1.PARTITION=@P9) AND ((T1.INSTANCERELATIONTYPE=@P10) OR (T1.INSTANCERELATIONTYPE=@P11))) AND ((((((T8.PARTITION=@P12) AND ((T8.PARTITION#2=@P13) OR (T8.PARTITION#2 IS NULL))) AND ((T8.PARTITION#3=@P14) OR (T8.PARTITION#3 IS NULL))) AND ((T8.PARTITION#4=@P15) OR (T8.PARTITION#4 IS NULL))) AND ((T8.PARTITION#5=@P16) OR (T8.PARTITION#5 IS NULL))) AND ((T8.PARTITION#6=@P17) OR (T8.PARTITION#6 IS NULL))) AND EXISTS (SELECT 'x' FROM ECORESPRODUCTCATEGORY T10 WHERE ((T10.PARTITION=@P18) AND ((T10.CATEGORYHIERARCHY=@P19) AND (T10.PRODUCT=T1.RECID)))) ORDER BY T1.DISPLAYPRODUCTNUMBER OPTION(FAST 4)

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Martin Dráb Profile Picture
    237,884 Most Valuable Professional on at

    Cross join is not a problem by itself, but you'll have to add a relation to EcoResProduct. You may need to do it in code.

  • Community Member Profile Picture
    on at

    Thanks Martin,

    I'm new to customization, so wasn't sure where I was going wrong. I could see how to set up relations in the AOT when adding multiple Data Sources to a Query, but couldn't see how to do it when adding multiple Data Source to a Form.

    I assume that if the Data Sources are tables and they have Relations already defined, then AX will know how to join them together, but for Views you can't set up Relations in the AOT and so you need to do it in code.

    I'll look at creating the relation in code, would this be in the form's init() method, or can it be done by overriding the data source's init() method?

  • Martin Dráb Profile Picture
    237,884 Most Valuable Professional on at

    Use addLink() method, e.g. HydProductAttributeValueView_ds.queryBuildDataSource().addLink(fieldNum(EcoResProduct, RecId), fieldNum(HydProductAttributeValueView, Product)).

    You can use init() method in either the form level or DS level. Form's init() calls init() of data sources.

  • Verified answer
    Community Member Profile Picture
    on at

    Thanks Martin,

    I'll give that a go.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans