Input Fields changing to random numbers after reload
Hello,
I have a data set I have split into multiple populations using population flag fields with a 1 for members in the population and null value for those not in it. I am trying to turn these population flag columns into INPUTFIELDs so that users can edit the members of a population. Data is loaded via SQL scripting of an ODBC connection to Snowflake. To try to create the INPUTFIELDs I took the population flags out of the main query and established them in their own query at the end of my load script (Picture 1).
EncounterID is a key field between not only the main table, SummaryTrauma, and this new Inputs table, but many others (Picture 2).
The Input Fields seem to work fine when first created in the desktop app and after subsequent desktop reloads. They allow the user to change the value and fall out of the population as expected when the value is not 1. Publishing to Access Point creates no issues either. However, after a QMC scheduled reload of the published QVW, the data is chaotic. In Access Point it still displays and seems to work well (Picture 3).
But when I open the same QVW with data from the same refresh in desktop, the population input field values have been replaced with seemingly random numbers (Picture 4).
I have tried using a VarChar flag of ‘Y’ or ‘N’ instead of this Int one and moving the creation of the Input Fields around in the load script, all to no avail. I’m thinking it may have something to do with joins and is trying to sum up the 1s while loading? Any suggestions for a fix or a replacement method that will allow users to change the members of a population?
