-
ProjInvoiceProposalListPage items not visible when Organization specified role is assigned to a user
ProjInvoiceProposalListPage items not visible when Organization specified role is assigned to a user.
There are 2 conditions to meet this limitation, having a custom role to a customer without admin privileges while setting "Grant specific organizations manually" and going directly from "All projects" > "Project invoice proposals".
As the issue do not happen with default roles, will be interesting if this possibility is also included with custom ones, allowing new security possibilities when accessing project invoiced without the need to go from another form.
This issue has been happening on last versions so it is supposed no one has come across this issue in the past.
-
Add to public information how system treats if a Finacial report name is a default one.
Financial reports are moved to default folder after using option “import default reports” or installing a service update.
System considers a financial report as a default one if they have at the end of the names the following segment “ - Default” (blank space, hyphen, blank space and default).
On the other hand, if the segment is not at the end of the name (for example, adding a dot after “Default”), any of the blank spaces is missing or hyphen is not the same one as in the other reports, issue will not be triggered.
Default word can be either in capital or lower case.
Example:
This triggers the issue: Test Financial Report - default
This does NOT trigger the issue: Test Financial Report- Default
This does NOT trigger the issue: Test Financial Report - Default.
This does NOT trigger the issue: Test Financial Report - Default new
Request is adding this to the public information to prevent anyone face this limitation.
-
LCS API usage with MFA enabled service account
Although using the LCS database movement API from Azure DevOps pipelines to perform database imports, exports, asset library access etc, worked like a charm using the authentication mechanism as explained here:
https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/database/api/dbmovement-api-authentication
But when MFA wants to be used by CA policy for that service account, this authentication fails. I know that this article describes that it will not work with MFA enabled accounts.
Our idea was to exclude "Dynamics Lifecycle Services" enterprise app (ID 913c6de4-2a4a-4a61-a9ce-945d2b2ce2e0) from that CA policy, but unfortunately, this app cannot be excluded as it cannot be found in that selction list. Neither by name, nor by ID, nor by Object ID.
Enable the API with services account which have MFA enabled will increase security, so it should be a possibility to be taken.