Sage 100

A customer just called - they're on Sage 100 Standard 2014 - claiming that one or more of their VI jobs suddenly has the wrong column # for some of the import fields. I've never heard or seen this before. Naturally, they are insistent that I ""check the knowledgebase"". Does anyone run into anything like this? From what I understand they claim their VI was pulling data for a field from column 5. Now they go in and say that it's pulling from a different column - perhaps column 7. The only thing I vaguely remember might cause this is swapping the VI source file type. Even then I can't recall running into this previously. Anyone else?

a little early, the full moon is not until tomorrow.

You laugh .. but I swear by that full moon... causes all sorts of crazy issues

Other thing that will change column number is the 'recalc' column button.

Also would Export a full set of the VI jobs after resolving this so when (I mean if) it happens again, you have another clue to the cause. I am stating the stuff we all do so I apologize if I seem too basic. It never hurts to document what we do.

One of those things that would be useful if ""Vi Job Changed"" was posted to the Activity Log.

Weird... There must be something to this full moon. My first post disappeared.

As for the moon, our bodies are 60% water. If the moon impacts the oceans...

@MoiraGoggin got it! I think (though customer denies remembering doing it) that someone went into VI, clicked the RECALC button. What this does is renumbers all the columns from that one forward. This was a pretty big VI job with about 40 columns. It's unlikely someone went through and changed each one by one. It had to be a manual ""recalc"" although customer denies being in the VI job recently. Note that there is no warning that this is going to renumber or do anything. The only way you can tell anything happened is to drop back to the data panel and view that the columns were renumbered. Sage should consider adding a warning similar to ""do you really want to renumber"" prior to making the change. It's not a big deal on a small VI but on larger ones it can be an issue.