JohnArniotis1
3 years agoQrew Member
Uploading legacy data with conditional drop down fields
Hello All,
This question may sound very simple but I am trying to find the most efficient way to tackle this issue and was wondering if anyone has run across this problem before.
I created a table to make a process more efficient for one of our departments. Long story short they still tracked items in Excel and had multiple versions of this tracker on random machines. There are multiple states that have different needs so I created a few conditional drop down fields to clean up what each user sees when creating a record. All of that works fine when entering a new record. In order to keep users from simultaneously working in QB and Excel I wanted to "normalize" the legacy data and import it into QB. I have already made sure the data fits the new form but when I go to import the legacy data none of the conditional fields will update with the values coming in from Excel. I guess that makes sense since a child record gets added to the tables holding the conditional values when a new record is saved and a simple upload may not allow for that to happen. I am thinking I will have to create a pipeline but wanted to ask if anyone has run across this issue and come up with a solution.
Currently I am testing this out with only one state, with minimal data, but if and when the broader release happens I am going to have to upload 10k plus records, so manual data entry is not an option.
Thanks in advance for any help you may provide.
------------------------------
John Arniotis
------------------------------
This question may sound very simple but I am trying to find the most efficient way to tackle this issue and was wondering if anyone has run across this problem before.
I created a table to make a process more efficient for one of our departments. Long story short they still tracked items in Excel and had multiple versions of this tracker on random machines. There are multiple states that have different needs so I created a few conditional drop down fields to clean up what each user sees when creating a record. All of that works fine when entering a new record. In order to keep users from simultaneously working in QB and Excel I wanted to "normalize" the legacy data and import it into QB. I have already made sure the data fits the new form but when I go to import the legacy data none of the conditional fields will update with the values coming in from Excel. I guess that makes sense since a child record gets added to the tables holding the conditional values when a new record is saved and a simple upload may not allow for that to happen. I am thinking I will have to create a pipeline but wanted to ask if anyone has run across this issue and come up with a solution.
Currently I am testing this out with only one state, with minimal data, but if and when the broader release happens I am going to have to upload 10k plus records, so manual data entry is not an option.
Thanks in advance for any help you may provide.
------------------------------
John Arniotis
------------------------------