-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Update issues-open-report-designer.md #1911
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Learn Build status updates of commit 4a1b1dd: ✅ Validation status: passed
For more details, please refer to the build report. |
support/dynamics-365/finance/financial-reporting/issues-open-report-designer.md
Show resolved
Hide resolved
Learn Build status updates of commit 023d552: ✅ Validation status: passed
For more details, please refer to the build report. |
Learn Build status updates of commit 5b69c20:
|
File | Status | Preview URL | Details |
---|---|---|---|
support/dynamics-365/finance/financial-reporting/unable-to-connect-financial-reporting-server.md | Details | ||
support/dynamics-365/finance/financial-reporting/issues-open-report-designer.md | ✅Succeeded |
support/dynamics-365/finance/financial-reporting/unable-to-connect-financial-reporting-server.md
- Line 43, Column 214: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#issue-2---the-user-isnt-assigned-the-required-permissions-to-use-financial-reporting' in 'dynamics-365/finance/financial-reporting/issues-open-report-designer.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 490f16e:
|
File | Status | Preview URL | Details |
---|---|---|---|
support/dynamics-365/finance/financial-reporting/unable-to-connect-financial-reporting-server.md | Details | ||
support/dynamics-365/finance/financial-reporting/issues-open-report-designer.md | ✅Succeeded |
support/dynamics-365/finance/financial-reporting/unable-to-connect-financial-reporting-server.md
- Line 43, Column 214: [Warning: bookmark-not-found - See documentation]
Cannot find bookmark '#issue-2---user-receives-Connection-attempt-failed-user-does-not-have-appropriate-permissions-to-connect-to-the-server-contact-your-system-administrator-message-when-trying-to-use-financial-reporting' in 'dynamics-365/finance/financial-reporting/issues-open-report-designer.md', did you mean '#issue-2---user-receives-connection-attempt-failed-user-does-not-have-appropriate-permissions-to-connect-to-the-server-contact-your-system-administrator-message-when-trying-to-use-financial-reporting'?
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 30a136d: ✅ Validation status: passed
For more details, please refer to the build report. |
Learn Build status updates of commit 5a03816: ✅ Validation status: passed
For more details, please refer to the build report. |
support/dynamics-365/finance/financial-reporting/issues-open-report-designer.md
Outdated
Show resolved
Hide resolved
Learn Build status updates of commit 71979ce: ✅ Validation status: passed
For more details, please refer to the build report. |
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.