cosmo-tech / azure-digital-twins-simulator-connector Goto Github PK

File '/home/pjeanmarie/APP/aio/Simulation/Resource/CSVFromADT/Family.csv', line 2: Cannot interpret value: 0 for enum DT_EnumAgingMethodology

We obtain this in csv file:

id
OMI
PostTimeSteplyYearUpdate
TimeSteplyUpdate

instead of this:

id,PostTimeSteplyYearUpdate,TimeSteplyUpdate
OMI,,

Related to this PR (which is mostly about improving performance), is there a reason to get twins by models (using a where is_of_model query) instead of fetching all twins at once (no filter on the query) and using their metadata to dispatch the data appropriately.

Not filtering on the model type should reduce the number of API calls and improve even more the performances. Should we do that in that issue/PR while we are at it?

Originally posted by @sjoubert in #50 (comment)

Corresponding JIRA issue : PROD-8163