Merge Customers fails due to false positive dimension conflicts on related items with identical dimension sets

[MadeleineCH]

Please include the following with each issue:

1. Describe the bug
When using the "Merge Customers" function, the system incorrectly flags dimension conflicts during the merge process, even when no real conflict exists.

2. To Reproduce
Steps to reproduce the behavior:

1.Create:

• Customer 1000
• Customer 2000

2. Create:
   • Item 1000 with dimensions: Department = SALES
   • Item 2000 with dimensions: Department = SALES (same as Item 1000)
3. Go to Customers.
4. Select Customer 1000.
5. Choose **Actions > Functions > MergeDuplicate.
6. Attempt to merge Customer 2000 into Customer 1000.
7. A dimension conflict is reported, although:
   • The customer-level dimensions are not conflicting.
   • Item 1000 and Item 2000 have the same dimension values.
   • No true data conflict exists.

Example Scenario:

• Item 1000 and Item 2000 exist and Item 100 have the same Dimensions like Item 2000

AL code snippet that demonstrates the issue or a link to a code repository the developers can easily pull down to recreate the issue locally.

Code in Table 64 "Merge Duplicates Buffer" function CollectRelatedTables()

Note: Because the developers need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient.

3. Expected behavior
The merge should check dimensions only for the target table (Customer, ID 18) and related ledger entries that are relevant to the customer. Shared or matching Item numbers and unrelated dimensions should not cause merge conflicts.

4. Actual behavior
The system detects dimension conflicts even when dimension values are valid. The conflict is falsely triggered due to dimension differences in Items (same Item No. used across different customers), even though these should not be considered in the Customer merge context.

5. Versions:

• AL Language: v15.0.1433841
• Visual Studio Code: 1.102.0
• Business Central: 26.0
• List of Visual Studio Code extensions that you have installed: AL Language only
• Operating System:
  • Windows
  • Linux
  • MacOS

Final Checklist

Please remember to do the following:

• Search the issue repository to ensure you are reporting a new issue

• Reproduce the issue after disabling all extensions except the AL Language extension

• Simplify your code around the issue to better isolate the problem

[qutreson]

This issue seems to be related to Application code in Business Central.

Let's get the issue to a team who will fix and backport it, as this repository is only for issues related to the AL compiler in latest developer preview environment for Dynamics 365 Business Central. We suggest that you open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.

To open a support case, you can:

• Open a support request to CSS through the PartnerSource portal
• Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.