Sage 100

Has anyone run into another fix for VI jobs in payroll under v4.4 PU6? I keep getting the ""Job Validations Contain Obsolete References that No Longer Exist In The Dictionary. Job Will Be Deleted"" Jim's fix is not working. http://www.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=525271 And it's erroring out on even a fresh new VI job for PR.DATAENT where I add in no fields. Just saving the job and re-opening it produces the error.

Did you look at Jim's other fix: http://community.90minds.com/2010/09/24/why-did-my-mas-90-payroll-import-delete-after-upgrading-to-v44/

Deleting the JC validations is crucial. If you are importing the job into v4.4, you have to delete them prior to exporting the job from the earlier version. I believe the issue is resolved in v4.5. I will test and report back.

Jim's suggested fix didn't work. I also cannot enter a brand new VI job without it kicking out the error. I suspect a Sage dictionary issue though I'm not looking forward to the cure of ""reinstall the whole shooting match"" just to see if it's a bad dictionary.

Wayne, Try looking at the following Resolution IDs in Sage Knowledgebase. Resolution IDs = 523429,432966,525271. Also when you first bring up a new VI job and select PR.DATAENT as the source file, click on the Perform button see what Job Perform Logic is listed - do you need it all? Or is only PR_DATAENT2 the only logic listed. Last weekend I was working on an installation version 4.40 w/ PU 4 and had similar issues.

I ran into something similar recently with VI - rather than resintalling we exported any good VI jobs in the current install, backed up the VI folder and the Vi files in the MAS_System folder - and copied my good files in. That seemed to resolve the issues we were having.

Does the validation have any references to job cost in it. If the client does not have job cost delete these out of the validation.

I just tried creating a new job in VI for Payroll Import on a 4.4 PU6 installation. Right after I enter in the job name I received the window ""Is this a new job? I said yes, immediately received the message ""Job Validations Contain Obsolete References that No Longer Exist in the Dictionary. Job will be deleted"". And it was. Didn't get even a chance to click on the Data tab or the Validation tab. BUT I went right back in and created the VI job a second time and it let me in and allowed me to set up the import job. I had to visit the Data tab and delete all references to Check_Bank Code, Job_Number and Cost_Code. I then visited the Validation tab and delete the above references (all per Resolution ID = 525271) I was able to save my VI job and then call it back up to continue to work on it. Hope this helps you!

Thanks - I'll check these out when I'm back on-site. Looks as if the Job_Number and Cost_Code may be two I did not try.

Any luck?

I'm going back out there next Thursday

Just FYI - I'm working on another customer's 4.4 PU 4 and the but where the VI won't even save a PR fresh job is not there. So it appears to have been introduced between PU4 and PU6 (which is the level I experienced the above issue).

Sorry false alarm - it also does not work if I save the job and then try to re-enter.

Yeah. You have to delete the job number and cost code fields from validation when you first create it.

Editing the VI7JOB.SOA file with DFDM also works. Delete validation for Bank Code, Job Number and Cost Code.

Good to know there is a back door. Always frustrating that it just blows without warning....

Had this issue today. The payroll import had been created in a prior version and obviously didn't upgrade. When it just deleted I had one of those moments - Can I recover from this? Fortunately found a backup, but not good it you have to change the import job or it gets deleted. To resolve the issue, first went to Sage - KB Archive. Found something, but no resolution as the status there is Engineering is Researching. A dead end!. Searched Socialcast and found this thread. Took the ideas and added the approach of editing VI7JOB. Client thinks I'm all powerful!! My comments added to enrich the technical value here.

I thought you WERE all powerful......