search

PardeeCenterDU / IFs-Issues-Tracking

This repository only holds the list of bugs that have been reported for IFs. Anyone may add a bug report, but please look to see if your issue has already been added!
2 stars 0 forks source link

Data Importing issues #252

Closed quciet closed 8 months ago

quciet commented 8 months ago

  1. The RA was not able to select a variable that has "&" in its variable name. In her case, the table was LandUrban&Built, the recording she did shows the problem. https://www.loom.com/share/337ab778fb4042a190d4a51155fe547d?sid=37f84ec9-4f3d-4a08-bf12-6964678a9b61

  2. After importing some tables, the process fails to store information in the DataDict table in the IFsDataImport. Not sure what caused the problem. There were 11 tables in total, but only 4 of their DataDict entries were saved.

Thanks, Yutang

samimck commented 8 months ago

Regarding issue 2, IFs gave this error after clicking "Accept Data" during data import. The examples are for SeriesLandAgri and SeriesLandTotal. Similar errors were thrown for other related land series.

LandAgriError LandTotalError
PardeeCenterIFs commented 8 months ago

Can we include here the original Excel file to import the data and reproduce the error.

samimck commented 8 months ago

Can we include here the original Excel file to import the data and reproduce the error.

LandAgri.xlsx LandTotal.xlsx

PardeeCenterIFs commented 8 months ago

These 2 don't seem to have "&" in the name.

samimck commented 8 months ago

These 2 don't seem to have "&" in the name.

oops! here's LandUrban&Built. LandUrban&Built.xlsx

PardeeCenterIFs commented 8 months ago

I don't think the first issue was priority 5, there was a workaround by just scrolling down and clicking in the listbox box below. Anyway I think we should create items individually.

  1. This one is fixed, but as I said there was a workaround by scrolling down and clicking directly in the list.
  2. I have fixed this one, the problem was that the DataDict.db field "Name in Source" has double quotes in its content: Item "Agricultural land". I'm now handling those quotes.

Both fixes will be included in version 8.11.