DataChangedConflict when Importing Purchases

Highlighted
Contributing Cover User JOberg
7 Posts
Contributing Cover User
Australia
Contributing Cover User

7Posts

8Kudos

0Solutions

DataChangedConflict when Importing Purchases

I have seen a solution for this where the answer is to remove the flag from Warn of Duplicates. This is not a good solution as it will then allow duplicates in the system which is never a good idea.

 

We have found that the problem occurs when the last purchase transaction was to convert an order to a bill. The PO Number on the original order is used as the PO Number on the Bill. The system then assumes that that number was the last used number which of course it probably is not.

 

The easiest fix is to record a new bill - can just be a dummy with no values. This will cause the system to recognise the true last number used and then the import will work.

 

I hope this helps others who have the same issue.

1 REPLY 1
Highlighted
MYOB Moderator Komal_S
622 Posts
MYOB Moderator
MYOB Moderator

622Posts

70Kudos

106Solutions

Re: DataChangedConflict when Importing Purchases

Hi @JOberg 

 

Thank you for sharing your experience with the Community Forum. I hope members of the Forum will find this information beneficial.


Please do not hesitate to post should you have other suggestions. 

Kind regards,
Komal

MYOB Community Support

Online Help| Forum Search| my.MYOB| Download Page

Did my answer help?

Mark it as a SolutionHelpful? Leave a to tell others

Didn't find your answer here?

Try using advanced search to find a post more easily Advanced Search
or
Get the conversation started and make a new post Start a Post