RE:
Please add this feature!! This is very much needed feature.
RE:
This behavior is causing our customer a lot of problems, please give it a high priority.
RE:
When transferring from GP to BC, multiple accounting users can face issues. In GP, saving a journal entry, even in different batches, increments the Journal Entry No. The renumber document function helps, but BC’s workflow for journal approval.
RE:
The requested feature is critical and only logical. As otherwise the vendor payment process is not seamless.
RE:
This idea should be expanded for all dataverse supported products which can be integrated with D365 Finance and can use tax calculation service.Below is list of products that support dual-write integration with Dynamics 365 Finance. Highlighted products can be taken into first priority for tax calculation use cases. Dynamics 365 Project OperationsDynamics 365 SalesDynamics 365 Supply Chain ManagementDynamics 365 Customer ServiceDynamics 365 Field ServiceDynamics 365 MarketingDynamics 365 HR
RE:
I get issues when trying to rename or drop columns in my Lakehouse table. In order to use %%ALTER TABLE ALTER COLUMN, I need to enable column name mapping. However after I enable the column name mapping, the table stops syncing properly to the SQL Analytics Endpoint.
RE:
After 8 years of the originally proposed idea, we still couldn't get the Shape Map with the label. ArcGIS already from ArcMap 10.4 evolved into ArcGIS Pro 3.3.
RE:
or even an option to hiding it
RE:
This happens most when transfer from GP to BC. Accounting has multiple users. GP once Save, even different batch, Journal Entry No. will go to next one. Renumber Document number function improve some, but if BC has workflow for Journal approval. It will cause problem in operation.
RE:
In production, this feature is very import to restore the lakehouse at ETL starting point when ETL process fails.Snowflake has one command to restore its warehouse to a time point