Now Available in Community - New TechTalk Videos for 2020
Read More about New TechTalks for 2020
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We added the Simulate posting feature in 8.0.2. We found that the validate functionality was not fully validating in some cases so we added this feature to fully execute the posting code up to the point where it actually posts.
This feature makes the Validate functionality obsolete. We are considering removing Validate and Validate voucher in the future. Do you have any issues with us removing the Validate functionality? It would not occur for at least 12 months after we announce it. Looking for feedback.
In my opinion there is nothing wrong with removing the validation, as along as simulation is providing an accurate view of posting entities. Financial consultants may have a view on this. Lets wait for their input as well.
From my perspective you can remove the validate/validate voucher in the future, as long as we have the (improved and better) simulate posting functionality :-)
+Ludwig and Sohaib
Users need either validate or simulate, all they want is how it would look after getting posted and if all data is good to get posted.
Simulate with additional option of showing which accounts and FD would be used and their posting types would be great.
Users would like to use a 'Validate' function. The simulation is better as it will indeed find related ledger setup and accounts to see if something is missing. However, there is a performance penalty. There are sometimes large journals imported (e.g. salary details from external app with more than 15000 lines) which do only use postings on ledger accounts and no sales tax is involved. For these journals, the validation is already sufficient and will perform quicker.
My feedback would be:
- Use the word 'Validation' used instead of 'simulation'. I think the validation word would be better for users understanding to start a check on journal entry.
- Have an option to do a short or deep validation. So probably open a dialog or have a setting per journal to define if a simulation will be performed during validation or not.
Thanks for the great replies! I appreciate candid feedback. If I can summarize a little: 1) Simulate should also show the entries that will get created and then let you post; 2) "Validate" still has some value due to performance in some cases 3) If we keep "validate", it should show entries as well.
sounds win win
Business Applications communities