-
Modified by option isnt reflection with data after changing batch job status
When you change job discerption on the batch job, you could see the modified by option is reflecting with the editor's name, however if he changed the status of the batch job this won't reflect with the editor's name. Please apply changes on this field to reflect with data after editing any field.
Thanks in advance.
-
[Dual-Write] - Date field value in CE different from FO field value
This is caused by a few things, mainly the field properties on the CE form and the type of column this data is stored as on FO side.
For CE, that ship date value on the Order form is a Date only field on the form with User Local behavior:
The different behaviors for that type of CE field, which says User Local behavior will modify the value to the current user’s timezone.
For FO, that table field doesn’t store the time because it is a Date field and not a Datetime field so when it is stored in SalesTable it doesn’t store the time or the time Zone information; when it is integrated to CE via DW it is just that date at midnight (ex: 12/10/2022 00:00:00). Then in CE when you open the form, that field date value will be modified based on the user’s time Zone. So if the user is GMT-6, 12/10/2022 00:00:00 turns into 12/09/2022 18:00:00.
-
Print management isn't supporting email body
We would like to suggest adding email body option within print management email notification set up for the customers who are unable to use ER or SSRS reporting. This would provide easier navigation instead of creating a whole process through ER or SSRS.
-
Clean up job for one time address
We would like to propose new feature or batch job to be implemented within F&O to clean up the one-time address from source table or to be truncated after a specific period of time
-
Net version
We would suggest informing customer via communication or internal Warrings with any Net version updates or any force update. Which will prevent any suspected regression on the customization which might be blocker for environment at some situations.
-
Known limitations with finance and operations tables
As reported on MS docs there are number of tables that have limitation with Azure synapse as shown on the following, our ask is to implement a work around for export from Azure synapse until we are able to rectify this gap or to added on the road maps.
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-select-fno-data#known-limitations-with-finance-and-operations-tables