web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Error using PSTL Item ...
Microsoft Dynamics GP (Archived)

Error using PSTL Item Combiner Utility

(0) ShareShare
ReportReport
Posted on by Community Member

I have run into a couple of issues with running the Item Combiner Utility.

Initially, I was receiving a primary key violation on table IV00101_pre20130515, IV00103_pre20130515 and IV00108_pre20130515.  I have no idea what this table is used for, and my partner was unable to shed any light.

I assume it has something to do with our inital conversion or work that was done on the DB at that time, but not sure.   Regardless, no data has changed in this table since 2013, so in our Test DB I deleted the primary keys on all three tables and ran the utility again.

This time a handful of items received a PK violation on IV00200.  Not sure why this would be the case, but I would like to resolve before trying in LIVE. 

My questions are 1) why would the combine utility be attempting to insert into a legacy (unused) table

2)  What to do about the other PK violation (IV00200)

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Bill Campbell Profile Picture
    Bill Campbell 12 on at

    Matthew, if you have a test database and it is still the older version, might you refresh the TEST data with more current version of the data by restoring a current backup onto the TEST data.  This will at least clear off any 'old data' inconsistency potential.

    Second on the table names - I believe - that the table with the extension _pre20130515 is a table that is not found in many systems.  If I were to guess, someone at some point made a backup of the table directly in the database - a short cut to making a full and proper backup.  But for PSTL to make any change to these tables is to say the least strange.  

    So, I would start with a clean database in TEST, remove the tables with the 'strange' appended names - you should see a table with the same IV00103, 108 and 101 in the list, but you do not require the other tables in the TEST database.  Just for sake of interest, are the tables in the TEST and the LIVE database?  Do you have OTHERS?

  • Community Member Profile Picture
    Community Member on at

    Thanks, Bill -

    We restore a backup of our live database into test every night.  The data in question is only a few hours old.  I have restored several times while testing, to ensure I had a "fresh" start each go around.  

    By removing the PKs, that error was resolved.  It looks like the utility ran a straight update in those tables, changing the OLD item value to a NEW value, as opposed to truly combining the records.  Understandable, I suppose, considering the fact that these are not standard tables.

    My concern now is with the IV00200 PK conflicts.  Any ideas on that table, as it is a production table and the errors concern me.

  • Suggested answer
    Bill Campbell Profile Picture
    Bill Campbell 12 on at

    Just for clarification - do you have the IV00101_pre20130515 table in your Production database - if so, what is the date on the table - you will find that in the SSMS window.

    Onto the IV00102 which is the Item Quantity Master

    Does the error provide more details on which Item it might be in conflict over?

    From everything that I know about the PSTL and the Item Combine or Change, it should be running thru all the tables that are effected and making the change everywhere it finds the 'old' item it replaces with 'new' or consolidates as needed.

    In looking at exactly what PSTL does - I am not the best to comment, but ITEM number is Item number and if you combine two numbers the system should go and find all occurances of old number and replace with new - weather a change or a combine.

    Maybe you can post a sample of the Error message you are getting on the update and a screen shot of the Table listing - showing the _pre20130515 tables in the list.

    Good luck.

  • Andrew Hall Profile Picture
    Andrew Hall 190 on at

    For info I came across a similar issue (primary key violation) with the account changer combiner for pstl. In the end traced it down to a third party that has alternate windows for accounts. Made a copy of the set file , removed the third party entries and used that , once I had finished with PSTL put the set file back.  This may be a similar issue if you have a third party that effects inventory

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans