Sage 100

Just took a call on this 2016.3 Advanced Description Error: ""The save/update credit card information to Customer credit card is required."" in Accounts Receivable Repetitive Invoice Entry and Accounts Receivable Invoice Data Entry Disclaimer Backup Warning Use caution when working with the below product functionality. Always create a backup of your data before proceeding with advanced solutions. If necessary, seek the assistance of a qualified Sage business partner, network administrator, or Sage customer support analyst. Cause The SaveCreditCard$ field is blank in the data file. https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=25088&sliceId=1&cmd=displayKC&dialogID=309549&docType=kc&isLoadPublishedVer=&stateId=309551&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

Sounds like the field is blank but the code is expecting a ""Y' or ""N"" So is it something that can be changed by checking and unchecking the button to save the credit card information? or di DFDM required to change it?

Sorry, this is yet another known product defect gone unfixed in product updates

perhaps we need another 90Minds group ""Sage100 Routinely unfixed problems

Print them out and wallpaper the room the MOTM Sage road ahead will be in.

Just an FYI - you can't fix this with VI . The SaveCreditCard field cannot be imported to. Had to manually edit 83 records with DFDM. ARGH!

Just had to do this on my demo system

My client has 601 records that need to be fixed!!! @GregStiles, I see the SaveCreditCard field in VI, but are you saying it doesn't work? WTF!!!

@BrettZimmerman If you find a way to fix this through VI LMK - I tried quickly and it wasn't readily apparent that it would work but I may not have put enough effort into it.

If I had that many records I'd try and do a quick button script to see if the business object allowed bulk update from """" to N.

VI lets you create the job and add the field, but on import VI errors with field cannot be imported to.

So if that field isn't writeable with VI, does that mean the same is expected via a Script? I wonder if we could edit the data dictionary to make that field writeable. Otherwise, anyone feel like doing some mundane heads-down tedious dfdm editing of 601 records? Lol

I got the Utility from Sage that apparently is being released with v2016.5 (.4 just came out yesterday) - but I can't post it until later. They wanted me to send them the applicable data file from all the client's companies but I got them to instead send me the utility.

I took a call on this earlier this week as well.

From Brett: This utility is used to change the flag for SaveCreditCard$ in AR_RepetitiveInvoiceHeader from blank ("""") to (""N"") Make a backup Copy file CX_FIXARCC to ..\MAS90\Utility folder Make sure you are logged into company needing resolution Run Syzcon from within Sage 100. At providex prompt type >Run ""..\utility\CX_FixARCC The number of records should appear that were fixed. **NOTE:** Have not used yet so be sure you backup first. IF you use this report back on how it worked.

Success! (on v2016.2) Easy-peasy. Glad we didn't have to fix these 7,596 records manually!!