Commerce-troubleshooting-migration_v-chgri #1946
Open
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
|
Learn Build status updates of commit a45c987: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
support/dynamics-365/commerce/toc.yml
support/dynamics-365/commerce/payments/adyen-connector-eft-terminal-id.md
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. |
|
Learn Build status updates of commit 0bbb1d9: 💡 Validation status: suggestions
support/dynamics-365/commerce/payments/adyen-connector-eft-terminal-id.md
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. |
PRMerger Results
|
|
Learn Build status updates of commit c75c34a: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
Learn Build status updates of commit 9bf10f2:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md | Details | ||
| support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md | ✅Succeeded | ||
| support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md | ✅Succeeded | ||
| support/dynamics-365/commerce/payments/adyen-connector-terminal.md | ✅Succeeded | ||
| support/dynamics-365/commerce/toc.yml | ✅Succeeded | ||
| support/dynamics-365/commerce/welcome-commerce.yml | ✅Succeeded |
support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md
- Line 9, Column 1: [Warning: h1-empty - See documentation]
H1 is required. Add content to your top-level heading.
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.
|
Learn Build status updates of commit d60fd7e: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
Learn Build status updates of commit 878e1ce:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md | Details | ||
| support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md | ✅Succeeded | ||
| support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md | ✅Succeeded | ||
| support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md | ✅Succeeded | ||
| support/dynamics-365/commerce/payments/adyen-connector-terminal.md | ✅Succeeded | ||
| support/dynamics-365/commerce/toc.yml | ✅Succeeded | ||
| support/dynamics-365/commerce/welcome-commerce.yml | ✅Succeeded |
support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md
- Line 9, Column 1: [Warning: h1-empty - See documentation]
H1 is required. Add content to your top-level heading.
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.
|
Learn Build status updates of commit f6d7584:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md | Details | ||
| support/dynamics-365/commerce/data-synchronization/commerce-offline-implementation.md | ✅Succeeded | ||
| support/dynamics-365/commerce/payments/adyen-connector-invoicing-sales-orders-fail-stale-authorization.md | ✅Succeeded | ||
| support/dynamics-365/commerce/payments/adyen-connector-store-commerce-app-error.md | ✅Succeeded | ||
| support/dynamics-365/commerce/payments/adyen-connector-terminal.md | ✅Succeeded | ||
| support/dynamics-365/commerce/toc.yml | ✅Succeeded | ||
| support/dynamics-365/commerce/welcome-commerce.yml | ✅Succeeded |
support/dynamics-365/commerce/data-synchronization/commerce-data-exchange.md
- Line 9, Column 1: [Warning: h1-empty - See documentation]
H1 is required. Add content to your top-level heading.
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.
|
Learn Build status updates of commit 175fa37: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
Learn Build status updates of commit a4c84f1: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
Learn Build status updates of commit 5399d44: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
#sign-off |
|
Invalid command: '#sign-off'. Only Microsoft employees can use this command. |
|
#sign-off |
|
Learn Build status updates of commit 11c2054: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
Learn Build status updates of commit 2e3fa96: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
Learn Build status updates of commit 75f3eea: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
|
#sign-off |
|
@v-chgri, I have copied this PR to the private repo for further discussion and edits: https://github.com/MicrosoftDocs/SupportArticles-docs-pr/pull/9955 |
|
FYI I can't view the PR in the private repo (I'm off the corpnet for 6 more weeks). So I won't be able to access any feedback or discussions there. You can email me with questions & updates at [email protected]. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
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.