-
Migrate Folder structure during export/import of MR reports using the report designer
While trying to migrate the MR reports from one environment to another environment using the export/import functionality available in report designer the folder structure is not migrated. The report definitions could be imported successfully but no folder structure can be created i.e. the report definitions were always imported into the root directory. The MR report export/import functionality should also allow the folder structure to be migrated as part of export/import process so that report definition along with folder can be created in the Target where report definitions are imported. -
Make Azure.Storage.Blobs” usable in X++ customizations
When one try and access file directories in a BlobStorage storage account from the F&O Operations page user received the error "409 conflict response code" Currently “Microsoft.WindowsAzure.Storage” can be used in X++ customization. Making Azure.Storage.Blobs” to be usable in X++ customizations would help to resolve the issue. -
Enable to back up usage data to allow users to restore the user settings
Many a time user have to clear the usage data to resolve issue while accessing the D365 FO URL. when user reset the usage data (General > Reset) to clear the user cache, the personalization is not getting deleted. But it will delete some selections or options enabled or disabled by the user and revert to MS standard selection. Currently there is no option to have user-specific selections back to normal even after clearing the usage data, as the user always has to remember which option it was selected before, after clearing the usage data every time. Usage data stores those kinds of user settings (user-specific selections). Clearing usage data deletes this, so there is no recovery. -
Ability to fetch permission details(CRUD) for the roles along with resource details and license information
The data present on the view permissions form (System Administration > Security > Security configuration) is required. Currently the available ways to fetch data resent on the view permissions form using the entity “System Security Permissions” or security reports do not exports the value as shown on UI level( view permissions form (System Administration > Security > Security configuration). We required the way so that permission details/ license details for objects can be fetched correctly as shown at UI. -
Enable the smmActivitiesEntity for O-data call
User have a requirement to call smmActivities OData entity in Power Apps to create activities. User can smmActivitiesEntity in the system but this one is not enabled for OData call.
We validated and tested the entity in standard 10.0.28 environment and can see for smmActivities the ispublic is No.
When this property(ispublic) is set to Yes, the entity is visible by using the OData application programming interface (API).
Since for smmActivities the ispublic is No it is not enabled for O-data call kindly enable the smmActivities for O-data call
-
Track the result returned from the Data management framework's package REST API
The result of the Data management framework's package REST API can be retrieved from the LCS logs so that customer can get details of result returned from the API later for their analysis purpose.
Link: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/data-management-api#getexecutionsummarystatus
-
Implement the User Log for new architecture or latest version
Hi team,
Recently the user log feature/form has been deprecated from system starting from the Jan 12 2024 (10.0.38/PU62). Customer were using this for tracking the user sign in and also to count and verify the consumption of F&O licenses.
Navigation: System Admin > Inquiries > User Log(User Log will be deprecated from PU 62)
The user log feature/form has been deprecated giving the replacement feature as "Track user sign-ins"
The "Track user sign-ins" can not be considered as the equivalent substitute for customers with large no of daily sign-ins due to restrictions:
1.The log only shows data not older than one month. In fact the document mentions to export data every days to help guarantee a complete audit trail, an IT administrator must complete this procedure every seven days. So one have to export every 7 days to ensure the audit trail using the "Track user sign-ins" unlike previous feature User Log where data was retained and can be viewed for much longer time frame.
2.The export is limited to 10000 rows that means if customer have large no daily sign-ins (say >5000) in such cases to maintain the audit trail IT administrator must export the data everyday causing more manual effort.
To summarize –
The new feature "Track user sign-ins" which replaced the old user log feature/form is not ideal replacement for customers with large no of user sign in daily and might require more manual effort/administrative cost for IT administrator forcing to export the User Login Events from LCS everyday and can not be considered as ideal replacement for old user log feature/form.
As mentioned in depreciation note for user log feature/form since user log was legacy page that was built for the older client/server architecture hence information on this page was not accurate and it was depreciated and new feature "Track user sign-ins" provided.
It would be better to have such user logs again in standard product based on new architecture to track user login information where data will be retained for longer period and allow IT administrator to have complete audit trail with less manual effort or having to export data daily.
-
Manage User groups in Finance And operation
User groups in Dynamics 365 Finance and Operations allows you to set up and group one or many users together into a group to allow access to perform a certain function, route workflow approvals, or even remove the ability to perform a function by excluding users from a user group.
To create user group: System administration > Users > User group
Currently there is no way to determine which all functionalities in the finance and operation is using the user group. Only way to confirm if any user group is used is manual and required lot of manual efforts like testing by trial and error.
If no of user groups is large in the system it will become difficult to manage user group manually hence it will be helpful to manage group more efficiently to get the details on which functionality /workflow is using the user groups.
You’re offline. This is a read only version of the page.
