Logging would have to be enabled in your "custom sync tool", but it could be something simple like trying to set a warehouse code on a comment line.

The error seems to be related to orders being charged tax & shipping at the same time. Tax only, seems to be no issue. Shipping Only, seems to be no issue. Both = error.

Usually the "Column is not in the IOList" warning is not because of trying to set a field on a specific line type, there is usually a specific warning for those instances.  You will need to review your custom sync tool that is writing the data to sage 100 via the BOI and compare fields that it is using SetValue on against the file layouts for your version.  Look for fields whose name may have changed or have been removed and for fields using the wrong data type (having a trailing $ for a numeric field or missing the trailing $ for a string field).

Matt,

Did you ever get to the bottom of this?  We're experiencing the same error when entering SO lines.

We're on 100 2020 Advanced.

If by "entering", you mean using the Sales Order Entry task, your issue is likely different and you may want to make your own thread with additional details.

However, assuming this is an issue that has popped up recently, I'll ask the following;

1. Have any UDFs have been removed from your system lately?
2. Have you installed or uninstalled any third party solutions lately?
3. Have you installed any product updates lately?
4. Have you upgraded sage 100 lately?

To be clear: the orders that are throwing this error have been imported via integration. It’s when they are opened in SO entry UI and line tab is engaged, that the error pops.

1. Have any UDFs have been removed from your system lately? No. 

2. Have you installed or uninstalled any third party solutions lately? Yes. Following 2020 upgrade.
3. Have you installed any product updates lately? Yes. Following 2020 upgrade.
4. Have you upgraded sage 100 lately? Yes. 2018->2020

No, never found a solution. Could never figure out how to increase the logging to indicate which field(s) were causing an issue.

Seems like you have a column in your primary grid or secondary grid that is no longer valid.  Have you tried resetting the grid for the panel?

To reset, following these instructions.

Right click empty portion of the panel, expand “Panel Settings”, click “Reset Panel”.

Only check these options and click OK.

Exit the task and launch it again.

Yes, thanks, that had been attempted without success.  The errors persist.

Then you likely have a deeper issue.  Could be data dictionary related or, if your answer to question 2 actually involves third party solutions and not just the upgrade, then one of them may be responsible. 

If you can get everyone out of the system and keep them out until you can complete the following test, then rename the "Links" folder under the MAS90 directory on the server to something else temporarily, then launch the task again and see if the issue persists.  If it goes away, it is related to one of your third party solutions.  Once you are done testing, rename the folder back to its original name ("Links").

Do you have Mapadoc by any chance?  I have seen cases where an incorrect sequence of installing it during an upgrade can cause data dictionary issues.