Sage 100

Uggh....Sage failing me again. Just did a 4.5 upgrade today...customer goes to create a custom lookup in SO Invoice Data Entry and it errors out. Go to lookup the error on the knowledge base and it is targeted for correction in version 5. Really nice! Now I have to tell the customer who JUST upgraded to 4.5 that a new error they are getting won't be corrected until the next version. Is that lazy programming or are they running on a skeleton crew in that department?

Is there an error message? Describe it more. Perhaps a member with the correct half of the brain can assist..........

Error 43 SWQMAN 12110 when accessing ALE Lookup when multiple UDFs exist for a table (and yes, they have multiple UDF's on SO Invoice entry) The error happens as soon as they click on the Custom button in lookup and it tries to load the list of fields. I have attached the Sage KB article too. Reference on Sage KB - Defect ID: 98492 (lol...I like how they call them defect id's now)

I have half a brain but it is pretty filled up and partially functional today.

Did you run the Lookup conversion utility?

I have one coming up that I will be testing with the same situation. Not good if they have to wait another level because they have already been waiting for this level for their payroll import utility.

I ran into this issue while running the conversion utility. Sage's solution is to reinstall about six tables related to the ALE's which effectively wipe out your customizations. ALE's have been a PITA in both v4.4 and v4.5. Will test one of these days in the alpha 2013.

Yes. I had ran the lookup conversion utility and it ran without error. @KathyPurkiss I agree, it is terrible if the customer just upgrades and you have to tell them the new error they are getting won't be fixed until the next version. If we get multiple customers with this error maybe we can get Sage to fix it now instead of waiting until v5 (2013).

Agreed. I try to tell people to test the upgrade. I find very few believe me that there's a need to test. That however is my insurance policy. If the customer assumed everything worked and didn't test then we are happy to re-engage as part of a change request with no guarantees.

Does this happen using an individual custom lookup from the field in SO invoice entry?

@WayneSchulz I agree. I always have my customers test with our test migration environment. However, it is items like this that don't always get tested because the customer forgets those small things (due to it being something they take for granted).

How do you word your testing requirements? Do you have a document they sign off on or do you just list it as an assumption in the proposal? I'm thinking something like: ""All functions used by <Company Name> will be tested by the appropriate user(s) and any issues will be communicated to <My Company> prior to the Go Live date."" Thoughts?

I have it in the upgrade proposal boilerplate. Remind me after vacation and I will send it to you. Am also working in EULA and credit card / Exchange uploading cards to Sage Vault.

Thanks @WayneSchulz - now go enjoy your vacation!

Wayne enjoys his vacation when there is a hot spot nearby........ John Shave should have some thoughts about this topic as I believe it is core to his value pricing Knowledge Transfer Agreements. Work smarter, not harder....

I'm working on a value-pricing proposal and I want to make sure my assumptions are good. I give them three options but I also include assumptions, such as, testing WILL be done! Many moons ago, we had a sign-off sheet that said something like, ""We have tested (yada, yada, yada) and are satisfied.....