Comments
Really wish Microsoft would reconsider this particular issue. It is a major problem for many of the reasons already expressed by others above.
The issue would likely not be present if the Item References could be used in place of Item No. everywhere else in the system where Item No. is used, but this is not the case and likely would be more difficult than changing all Item No. character length throughout the system.
I would have expected this to be changed when the Serial/Lot No. was expanded, but unfortunately the job was left half done.
Fingers crossed that you reconsider this one soon.
Most of the above topics are already supported now.
Something that could be improved still:
Our solutions are delivered as managed, its not possible to edit the environment variable values after import via the solution. For this you need to go to the default solution first and search and edit the environment variable from there.
Would be nice to redirect the user to this setup when trying to edit the value from the managed solution.
We didn't test but as stated in the original post it would be nice to also ask during import the values for environment variables in case its type Decimal Number, JSON and Yes/No if not already done.
There are many similar tools available for this type of conversion. If you want an easier yet powerful and cheaper solution then opt ost to pst converter by magus tool. It is a brilliant tool with no technicality
Need to enable emailing via shared mailbox for Modern Authentication by October 1st, 2022. Many clients use the same common mailbox to send customer or vendor facing notifications for shared workload distribution. We cannot expect clients to have individual users send the customer and vendor notifications and not being able to share the replies and collaborate.
We need to know the status of the Azure Synapse Link replication of data from Dynamics 365 Customer Experience (CRM) to an Azure Synapse Workspace. This is a "must have" requirement to since if the replication has failed then systems / people may be using old (invalid) data. Please add reporting / alerting features.
This idea is related to the following changes that were added with BC 17:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-report-triggers?tabs=current%2Crdlc#modes
and to the design principles for designing reports:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-report-triggers?tabs=current%2Crdlc#multiplepreview