XDS issue when defining two different XDS policies on the same Constrained Table

Hi,

We have an interesting issue that has been seen post our upgrade to R2. Pre-R2 we had some XDS policies defined and working. Note that two of these policies were defined with the "LedgerJournalTrans" table (constrained table) and DimAttributeValueCombination as the primary table. Both these policies constrained the LedgerJournalTrans table with a free-form expression in the "Value" property. Here are the two property values:

Policy 1 with LedgerJournalTrans as constrained table- value = ((DimensionAttributeValueCombination.RecId == LedgerJournalTrans.LedgerDimension) || (LedgerJournalTrans.LedgerDimension == 0))

Policy 2 with same LedgerJournalTrans as constrained table - value = ((DimensionAttributeValueCombination.RecId == LedgerJournalTrans.OffsetLedgerDimension) || (LedgerJournalTrans.OffsetLedgerDimension == 0))

Basically, one filters by ledgerdimension field and the other by offsetledgerdimension.

Post R2 behavior:

Upon launching the TaxAccountGroup form from General Ledger > Setup >SalesTax> Ledger Posting groups

an exception was seen "Max. num of joins allowed (99) is exceeded" and the form would not open. Note that There is no customization done to this form.

I debugged and discovered that upon disabling one of the two policies in question above, (i.e the two on the same LedgerJournalTrans table as the constrained table), the error goes away. I also worked around it by overriding the executequery() on the datasource of the form TaxAccountGroup as:

{

    xdsservices.setxdsstate(0);

  super();

   xdsservices.setxdsstate(1);

}

This worked by temporarily disabling xds. My question is - Has anyone dealt with this before ? Is it not good to use the same constrained table on two separate xds policies ? Any thoughts/comments would be appreciated.

thanks.

We have implemented a temp table called MyCostCenters with the XDS() method.

What is seen post R2 -