Comments
I'm taking a break from configuring 420 mobile device steps (all with promoted fields and some with detours) to beg Microsoft to add data entities for mobile device steps to the standard product.Let me do what I can to help. You'll need five data entities:Mobile device steps - WHSMobileAppFlowStepMobile device steps translated text - WHSMobileAppTextMobile device steps promoted fields - WHSMobileAppFlowStepPromotedFieldSetupMobile device steps detours - WHSMobileAppFlowStepDetourMobile device steps detours field to send - WHSMobileAppFlowStepDetourFieldSetup
We utilize BC for 5 different companies and use the Inter Company function directly in the Purchase Orders and Purchase Invoices but the Sales Tax does not follow the entry and ends up staying the originating company which is incorrect. There is risk to the Sales Tax not being transferred over manually as our AP system is now mostly automated with AI and there is no efficient process for being able to review IC entries posted entries and manually transfer the Sales Tax amount with an IC Journal. We would be very appreciative to have the IC function fully account for transferable taxes between companies.
Dear Mr. Totovic - are you aware that the mentioned migration routine is changing current data in the swiss-version of D365 BC so it becomes unusable/wrong after the migration to BC28? I think the new FCY-Module should be postponed to be automatically activated in BC28. We tried to explain the circumstances to the support-team but they did not understand the case.
From a compliance perspective, I think we should be able to prove to the auditors that we have deliberately chosen not to deploy a feature, so a function to give a feature a governance state would be ideal. This should come with an audit trail, so the lifecycle of a feature can be documented.