on
RE:
This tool also should only allow to change translations that are tagged by a change/new in the original label,caption,tooltip,.. or by a manual tag by an admin, because of a wrong translation.I hope this will prevent many erroneous translations done by search and replace.And i think this will reduce the need of automatic translations, because there will not be so many entries.
RE:
Extremly needed - agree
RE:
This issue needs to be actioned as we are manually reclassing all the journals that posted on the wrong GL Code. Just only concerned, why we implemented the bundle products if we never check the GL side of it
RE:
I should mention the "external claim number" field is an enhancement we did to Dynamics because each deduction needs a tracking number. That number is provided by the customer and relates to something in their internal systems. Any dispute of deductions requires this number when interacting with the customer. The External claim number referenced in step 9 is not required as part of the feature request for zero-dollar payments.
RE:
Having worked with a number of Canadian & US clients that deal with cross border operations that are buying in a different currency it would be great to have this feature out of the box.
RE:
I have no idea why this hasn't gotten more traction or hasn't been implemented yet. Seems like easy low hanging fruit that could add a lot of family and save development time.
RE:
I have no idea why this hasn't gotten more traction or hasn't been implemented yet. Seems like easy low hanging fruit that could add a lot of family and save development time.
RE:
This is another feature that's available in Excel, but not in Power BI, as we try to get our users to work more in Power BI, rather than constantly exporting to Excel, we need to be able to offer the same formatting. While formatting each column is way to achieve this one, it's a very tedious solution
RE:
I agree that this should be possible as it would be incredibly useful and save a lot of work.
RE:
1000% agree.