Open RDmitchell opened 6 months ago
Instance: production SHA: 1dc901360 Org: LBNL 200 Data set: ESPM Import Test
The program got further, to Geocoding, and then appeared to get stuck there
It seems that Geocoding is causing a 200 error. This was importing the ESPM report as an Excel file, not using the SEED / ESPM login feature
Instance: dev1 SHA: f5fc3b772 Org: LBNL 200 Data set: EPA Test Import
Mapping Mapping Review Finding Inventory Matches -- 200 error
It would appear that the MapQuest API key is invalid.
But I don't really want to have geocoding on anyway.
nstance: dev1 SHA: f5fc3b772 Org: LBNL 200 Data set: EPA Test Import
If I uncheck the geocoding fields, the import gets past the Geocoding 200 error.
Got through the entire import
I guess we need a way to bypass the geocoding step in mapping if there are problems with the geocoding settings? Either the API or the fields set for geocoding?
Need to give the user some information about how to deal with this.
Instance: production SHA: 1dc901360 Org: LBNL 200 EPA Test Import cycle and data set
Unchecked the Geocoding fields in Column Settings, and then the program could import the Custom Report Template from the ESPM login in SEED.
Seems like we need to have more user help about this problem.
@RDmitchell - How would you feel about the following error message?
instance: production SHA: 1dc901360 Org: LBNL 200 ESPM account logged into from data import in SEED: SEED_City_Test ESPM Custom Report Template selected: SEED City Benchmarking Report, which has 4 records in it
I logged into the ESPM account from the Data import dialog box in SEED, selected the template, mapped the fields, and then the "Finding Inventory Matches" dialog box appeared, and appeared to generate a 200 error
This is similar to another user's experience doing the same thing, for an ESPM report with only 10 records in it.