Skip to content

Conversation

@blauerPCL
Copy link
Contributor

@blauerPCL blauerPCL commented Jul 1, 2025

Summary

Update to include migration of Dynamics SL Product Classes to Business Central Inventory Posting Groups

Work Item(s)

Fixes # AB#567570

@blauerPCL blauerPCL requested a review from a team as a code owner July 1, 2025 04:20
@blauerPCL blauerPCL requested a review from JannikBausager July 1, 2025 04:20
@github-actions
Copy link
Contributor

github-actions bot commented Jul 1, 2025

Could not find linked issues in the pull request description. Please make sure the pull request description contains a line that contains 'Fixes #' followed by the issue number being fixed. Use that pattern for every issue you want to link.

2 similar comments
@github-actions
Copy link
Contributor

github-actions bot commented Jul 1, 2025

Could not find linked issues in the pull request description. Please make sure the pull request description contains a line that contains 'Fixes #' followed by the issue number being fixed. Use that pattern for every issue you want to link.

@github-actions
Copy link
Contributor

github-actions bot commented Jul 1, 2025

Could not find linked issues in the pull request description. Please make sure the pull request description contains a line that contains 'Fixes #' followed by the issue number being fixed. Use that pattern for every issue you want to link.

@blauerPCL
Copy link
Contributor Author

@nikolakukrika Here is the PR for the SL Product Class to BC Inventory Posting Group migration update. The AL Test Tool tests are also included.

@JesperSchulz JesperSchulz added the Integration GitHub request for Integration area label Jul 1, 2025
@JesperSchulz
Copy link
Contributor

@blauerPCL, it would look like this PR combines the changes from the previous two ones as well? That's ok, I'll manage somehow. But next time, try to make 3 separate PRs, not incremental ones. Or if you do incremental ones, then delete the previous two, as the last one will contain all changes.

@blauerPCL
Copy link
Contributor Author

@blauerPCL, it would look like this PR combines the changes from the previous two ones as well? That's ok, I'll manage somehow. But next time, try to make 3 separate PRs, not incremental ones. Or if you do incremental ones, then delete the previous two, as the last one will contain all changes.

@JesperSchulz , Sorry, maybe I am doing something wrong. I created 3 separate PRs; #28809 , #28812 , and #28819. Is it because I have multiple open PRs at one time? Even though I have pulled from Main multiple times, these older commits still show up when I create a new PR. For example, I'm getting ready to submit a new PR and my branch is showing that it is 18 commits ahead of microsoft/ALAppExtensions/main with commits going all the way back to May. This new PR should only have 4 small commits over the last 2 days.

@JesperSchulz
Copy link
Contributor

This PR has been merged. As it has a lot of merge issues, I'll just close it. I will sync this repo with the latest changes from ADO to get those two repos aligned again.

@JesperSchulz JesperSchulz added the ships-in-future-update Fix ships in a future update label Aug 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Integration GitHub request for Integration area ships-in-future-update Fix ships in a future update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants