Sage 100

Job validations contain obsolete file references that no longer exis...Job will be deleted"" PR.DATAENT I know this thread exists somewhere on this site but I can't find it. MAS 90 v4.4 - PU 2 & 3. Trying to move client from v4.3 to v4.4. PR VI keeps getting deleted. Above is on Sage KB, however, Sage CAN'T duplicate. The VI works great on our server (MAS 200) but not on client side. When I create a new PR import selected only the required fields, save it, then access it again, the mini VI gets blown away also. The only thing I can see that is different is that the client does not have all the modules that our office installation has so my theory is that one if the missing modules is causing this issue. Client has Module List: ,AP,AR,BR,CC,CM,FL,GL,LM,OI,PR,RM,VI. Job Cost is not installed so I am wondering if this might be causing the problem...........

I think @jimwoodhead posted something about that. I think you delete the validation in 4.30 and import the job into 4.40 and reset Te validation. There may even be a post on 90minds.com.

I had this problem on a Payroll import too. Raised holy heck with Sage and they all ""felt my pain"" but it's yet to be fixed. Jim Woodhead did this writeup http://community.90minds.com/2010/09/24/why-did-my-mas-90-payroll-import-delete-after-upgrading-to-v44/ And in my case Sage logged in and knocked a bunch of table validation out and then informed me that validation was no longer needed in 4.4 for PR (wrong). Ultimately I set up a very small validation on only the employee and earnings code and the import proceeded to work. Definitely a Sage bug in the data dictionary tables. They're probably holding back fixing it because they queried for payroll users who own VI and came up with a lower number of licensed users.

Really? Probably half of my PR customers import time.

That is the one I was looking for on this site but the history only seems to display for 7 days before it goes somewhere else. Is there a search feature somewhere? But back to the issue at hand. What Jim posted is just a theory with tech support. The problem is they can't duplicate the problem. When Jim originally posted, I thought to myself that the problem was odd because I have several clients on v4.4 doing PR imports WITHOUT the issue. Then my client popped today with the issue. The VI works great on my server, but the moment I open it on theirs it blows up and self destructs. I spent 30 minutes rekeying it on client side. I save and reopen, it self destructs. I create an import using only the required fields. Save and open. Self destructs. It ISN'T the bank code file. I really feel that it is caused by not have the same modules installed on both system. I have most of them, the client only has the ones indicated.

Just disproved my JC theory. Logged onto another v4.40.0.3 client with PR, VI but not JC. Created a VI PR entry with only the required fields. Saved. Pulled it back up. VI did not self destruct. No error message at all.

Could the VI module be ""broken""? Have you tried reinstalling VI? As a drastic measure you could export all their jobs out as EXP files, rename the VI directory then reinstall VI. Then import their jobs in or recreate.

Interesting thought. Will do that next week when I visit again.

Jeff, I just had the same thing. I went back into 4.30 and delete the Job Number and the Cost Code from the validation, exported and imported into 4.40 and it worked fine. I also recreated it from scratch as you described and it deleted it. It looks like deleting the JC validation is the key.

I agree the validation are the issue. If VI can't convert the validation or it feels it is incorrect it will delete the VI Job upon opening. It you remove the validations (delete them all) prior to migrating or exporting when you open it it up you can click the reset validations on V4.4. that should always work.

@jimwoodhead I tries that too and it didn't work. Creating one from scratch in 440 didn't work either.

It definitely sound like Sage added a bad validation line on one of the PU so called fixes.

Problem solved with client as Robert noted above. To test my theory, I set up a test PR import using only the required fields (why waste time on others). I then deleted ALL JC validations in the import. Saved job and reopened. Job was not deleted. I then deleted the JC validations in the v4.3 import, then exported. Imported into V4.4. Opened job in maintenance. Job did NOT delete. Problem solved. And as Robert noted, adding the JC validations back don't work either.