on
RE:
Worst of all, no window title! So you can't leave a refresh running in the background and check your taskbar for when it is done, you must keep switching to the window doing the refresh. (Same for uploads, etc.). A window title that changed from "Refreshing... Dataset X" to "Refresh Complete: Dataset X" would be a great help. And for uploads, "Replace dataset?" "Choose Folder" etc. as well as "Uploading..." and "Uploaded" so it's obvious when an action is required.A taskbar icon that indicated completed status would be the cherry on top.
RE:
I also think it is important to have a feature that allows you to speed up inbound flows in intercompany transactions
RE:
I think this is not a good idea, to have this global setting, because it would reduce the number of possible lines to be inserted in worksheets and document lines.Nobody stops you to reduce the line number increment while importing the lines into the journal, but i would not generally reduce the line number inclement.
RE:
For the ADF team, this is the feature that Janez is referring to: learn.microsoft.com/en-us/power-apps/developer/data-platform/bypass-custom-business-logic?tabs=sdkIt seems like it would be very easy for you to provide a way to provide these flags as part of the Dataverse connection. This would be a huge benefit to ADF and Power Platform developers and architects.
RE:
This Feature also does not allow for Discard Recon Reasons to create a Journal without a Vendor Line. Microsoft needs to re-do this feature to ensure it does not regress other TMS functionaltity.
RE:
Maybe the Dampener Period or a similar field would apply? Or if you reschedule a production order with a reservation it should never remove the reservation except with user interaction ("do you want to remove the reservation on this order?")I Upvoted this
RE:
This sounds like Production Families but maybe with some extra features to make it more viable in some situations. Please review how a family works (which is terribly documented) and maybe rewrite the ask?Since you can output the co-products of the family individually, the tree log example would mostly work... The challenge would be that each item has it's own BOM (presumably with one common component on each) and pro-rating the actual amount of the tree between the items is the tricky part in this. https://learn.microsoft.com/en-ca/dynamics365/business-central/production-how-work-familyhttps://community.dynamics.com/blogs/post/?postid=fecdcec5-05f2-4650-8f65-0098ab458f39
RE:
*This should be corrected so that the visual places employees in the correct location when a city name exists in multiple states.
RE:
Agreed. Having the ability to govern what gets propagated via shortcuts would be a massive help and also work toward a better "OneCopy" approach to data in OneLake. In cases where you want certain lakehouses/workspaces to only house specific data, the only current option is to basically duplicate data into a lakehouse.