Add multiple TSGs related to Inventory Costing #1975
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Clarified the error message context and updated table references in the symptoms section.
Contributor
|
Learn Build status updates of commit 741ae26:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| support/dynamics-365/supply-chain/costing/unable-to-edit-a-record-in-table.md | Details |
support/dynamics-365/supply-chain/costing/unable-to-edit-a-record-in-table.md
- Line 4, Column 9: [Warning: author-not-found - See documentation]
Invalid value for author: 'Soumyamoy Das' is not a valid GitHub ID. - Line 0, Column 0: [Suggestion: filename-contains-stop-word - See documentation]
Stop words like 'a', 'or', 'and', 'the', and 'in' are discouraged in filenames.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Updated the resolution section to clarify the causes of the error and best practices for executing inventory reversals.
Clarify error causes and best practices for reversals
Contributor
|
Learn Build status updates of commit 8f6d2ac:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| support/dynamics-365/supply-chain/costing/duplicate-reverse-is-not-allowed.md | Details | ||
| support/dynamics-365/supply-chain/costing/unable-to-edit-a-record-in-table.md | Details |
support/dynamics-365/supply-chain/costing/duplicate-reverse-is-not-allowed.md
- Line 4, Column 9: [Warning: author-not-found - See documentation]
Invalid value for author: 'Soumyamoy Das' is not a valid GitHub ID.
support/dynamics-365/supply-chain/costing/unable-to-edit-a-record-in-table.md
- Line 4, Column 9: [Warning: author-not-found - See documentation]
Invalid value for author: 'Soumyamoy Das' is not a valid GitHub ID. - Line 0, Column 0: [Suggestion: filename-contains-stop-word - See documentation]
Stop words like 'a', 'or', 'and', 'the', and 'in' are discouraged in filenames.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Added troubleshooting guide for fiscal period not open error during inventory operations.
Create troubleshooting guide for fiscal period error
Contributor
|
Learn Build status updates of commit 22d92e6:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| support/dynamics-365/supply-chain/costing/duplicate-reverse-is-not-allowed.md | Details | ||
| support/dynamics-365/supply-chain/costing/Fiscal-period-is-not-open.md | Details | ||
| support/dynamics-365/supply-chain/costing/unable-to-edit-a-record-in-table.md | Details |
support/dynamics-365/supply-chain/costing/duplicate-reverse-is-not-allowed.md
- Line 4, Column 9: [Warning: author-not-found - See documentation]
Invalid value for author: 'Soumyamoy Das' is not a valid GitHub ID.
support/dynamics-365/supply-chain/costing/Fiscal-period-is-not-open.md
- Line 0, Column 0: [Warning: filename-invalid-character - See documentation]
Only lowercase letters, numbers, and hyphens are allowed in filenames. - Line 4, Column 9: [Warning: author-not-found - See documentation]
Invalid value for author: 'Soumyamoy Das' is not a valid GitHub ID.
support/dynamics-365/supply-chain/costing/unable-to-edit-a-record-in-table.md
- Line 4, Column 9: [Warning: author-not-found - See documentation]
Invalid value for author: 'Soumyamoy Das' is not a valid GitHub ID. - Line 0, Column 0: [Suggestion: filename-contains-stop-word - See documentation]
Stop words like 'a', 'or', 'and', 'the', and 'in' are discouraged in filenames.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Contributor
|
Learn Build status updates of commit 005f188:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| support/dynamics-365/supply-chain/costing/duplicate-reverse-is-not-allowed.md | Details | ||
| support/dynamics-365/supply-chain/costing/fiscal-period-is-not-open.md | Details | ||
| support/dynamics-365/supply-chain/costing/unable-to-edit-a-record-in-table.md | Details |
support/dynamics-365/supply-chain/costing/duplicate-reverse-is-not-allowed.md
- Line 4, Column 9: [Warning: author-not-found - See documentation]
Invalid value for author: 'Soumyamoy Das' is not a valid GitHub ID.
support/dynamics-365/supply-chain/costing/fiscal-period-is-not-open.md
- Line 4, Column 9: [Warning: author-not-found - See documentation]
Invalid value for author: 'Soumyamoy Das' is not a valid GitHub ID.
support/dynamics-365/supply-chain/costing/unable-to-edit-a-record-in-table.md
- Line 4, Column 9: [Warning: author-not-found - See documentation]
Invalid value for author: 'Soumyamoy Das' is not a valid GitHub ID. - Line 0, Column 0: [Suggestion: filename-contains-stop-word - See documentation]
Stop words like 'a', 'or', 'and', 'the', and 'in' are discouraged in filenames.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Updated troubleshooting documentation for the error message regarding transactions that cannot be reopened due to pre-closure. Clarified symptoms, resolution steps, and added mitigations for handling the issue.
Contributor
|
Learn Build status updates of commit 948a86d:
|
This document outlines the error message encountered during inventory closing and provides resolutions for budget control issues in Dynamics 365.
Contributor
|
Learn Build status updates of commit cba802d:
|
Contributor
|
Learn Build status updates of commit c216012:
|
Added troubleshooting documentation for inventory closing errors.
Contributor
|
Learn Build status updates of commit 2b65548:
|
Updated the error message and resolution details for inventory closing issues related to negative on-hand inventory.
Contributor
|
Learn Build status updates of commit bb412ee:
|
Contributor
|
Learn Build status updates of commit a7e6413:
|
Contributor
|
Learn Build status updates of commit fb81835:
|
Added troubleshooting documentation for inventory closing errors related to processing levels and bundle totals.
Contributor
|
Learn Build status updates of commit 44a3cc1:
|
Contributor
|
Learn Build status updates of commit cb3119e:
|
Added troubleshooting information for the error related to account numbers during inventory closing.
Contributor
|
Learn Build status updates of commit 7771922:
|
Added documentation on inventory transactions posted at different cost prices, including symptoms and resolution.
Contributor
|
Learn Build status updates of commit 6551381:
|
Updated the resolution section to reflect the correct navigation path for rebuilding the Trial Balance.
Contributor
|
Learn Build status updates of commit fe8312e:
|
Document the behavior of already closed inventory transactions being reopened and adjusted, including symptoms and resolution.
|
Microsoft authors of articles need to make updates through the private repository, so the updates can be staged and validated by current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged. It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows: Public repo URL: We have closed this pull request. Please resubmit the updates through the private repo. For more information, see the contributor guide. |
Contributor
|
Learn Build status updates of commit eda3363:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Clarified the error message context and updated table references in the symptoms section.
Pull request guidance
Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.
We also need your help in order to process your request as soon as possible:
We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.
After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.