Breaking news from around the world
Get the Bing + MSN extension
Check out the latest Retail updates!Learn about the key capabilities and features of Dynamics 365 Retail and experience some of the new features.
Download overview guide | Watch Retail video
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View 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 | Talent TechTalks | Upcoming TechTalks
Hello Retail experts
I am facing an issue here. Wonder if you can help. When I try to calculate a statement I get an error "1 transaction not validated". I ran the "Validate store transactions" job but still no joy. The issue is happening with 3-4 shifts. Screenshots attached. Any insights? Thanks.
This is a part of new validation added to Dynamics 365 to make sure that all the transactions has reached the HQ and the data integrity is OK. You can run the "Validate store transactions" batch process, at Retail > Retail IT > POS posting manually which would validate the transaction. I would recommend to configure the job as recurring (3 or 4 times day or once before you run the calculate statement batch job), so that all the transactions would be validated by the time you post the statement.
Please refer below link for more details on the recent enhancements to Retail Statement Posting.
This can only be fixed by Microsoft and they fixed it after I raised a case with them.
Thanks for updating. Any idea what was causing the issue ?
Yes. It was a bug. This keeps happening with others also. They ran a script and fixed it.
Business Applications communities