Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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
This is going to be a more wordy post than usual as I have no screenshots of the issue or resolution.
When I returned to the office on Wednesday after being away at reIMAGINE for a few days and then being on holiday in Kentucky, I was asked for assistance by Jason on our service desk.
A client had logged an issue with a PO; lets say the PO Number was PO34791 for the sake of argument (I don’t actually recall what it was).
When the PO Documents Enquiry (Inquiry) window was used, the PO looked fine; the creditor (vendor) was the correct one and all other values were okay and the PO showed as received.
However, the PO was also showing in PO Entry with a different creditor id.
Jason showed me two SQL queries;
All very unusual.
I ran another query against POP10100 WHERE PONUMBER LIKE ‘PO34791%’ and this returned two lines of information both showing a PONUMBER field of PO34791.
in SQL Server Management Studio I dragged the values from the recordset into the query window to compare them; one was shorter than the other. The cause was that one of them (the one for the Vendor ID 1st001) contained a control character which is why it appeared shorter.
We’re not sure what the user had done, but the second, incorrect, PO was entered with a PO Number containing a control character; they’d been able to successfully enter the PO, but GP was then becoming confused about which one should be loaded when the user typed, or did a lookup, for PO34791.
We copied the live company into test and deleted the second PO (for vendor 1st001) from all tables (it had lines and tax and so on) and then verified the data with a Check Links and Reconcile and asked the user to double check.
This process would then be repeated on live with the PO being re-keyed (it was only a single line).
Read original post Weird Duplicate PO Issue at azurecurve|Ramblings of a Dynamics GP Consultant
Business Applications communities