Microsoft Dynamics App Pulls from One Field and Not Another

"In general, what can cause any kind of app to pull data from the wrong field?"

This must be some design, code, connectivity issue or all together as that app data pull is based on some written or generated code - right?
In simple words - "an application bug" in my opinion unless is some sort of "intelligent" app and in that case some algorithm needs to be reviewed but essentially a simple bug somewhere.

Oh, and here's one crucial element that I forgot to mention.  In a test environment, the app's file pulls data from the correct field.

Ironically, the issue only occurs in our live environment.

As best as I can tell, there is no substantive difference between the two environments.

Thanks, for the quick response!

If there are any further thoughts, please let me know.

John

is by any chance the app getting the data from a field using its "index number"?
can you make sure your test env doesnt have any added fields for debugging processes?

So that would be the proof that some setting/code is different in Prod than in Testing/QA and if there are not much details about the source code that "pull data from the wrong field" I would use SQL Profiler to see where is it coming from but this is based on assumption that you know at least what it that "..wrong field". What I'm trying to say is that you need to know something specific (like what this wrong field is, or what module does the pull to compare it with testing) in order to walk the thread and find where the issues is in order to fix it - right?

another shot, the app migth be taking the data from an outdated view and not directly from a table.

"you need to know something specific (like what this wrong field is, or what module does the pull to compare it with testing)"...

I do know what the wrong field is, as well as all of the other pertinent details.  I simply don't know why the issue is happening in prod and not in test.

John

John, is this issue solved?

No, I'm afraid not.

I don't have much to add unless you can show us this APP feature.
I guess best shot is that applications isn't using the field name but the field position in the table and for some reason the field position is different from development environment compared to the production environment.