Skip to main content
A
AP_958723617-Peridot
17-Peridot
April 30, 2022
Question

DataExport for datatables

  • April 30, 2022
  • 3 replies
  • 1459 views

I exported datatables separately from one server using (to file, single data, datatables option) and import in another server using (from file, data, file repository, browse) to get the values in it. Once import is successful, not able to reimport the same file again any servers. .import file also not present. then what is the reason for this skipping import while reusing same file. If i exported again, then that file is importing successfully for only one time. How to reuse the file?

3 replies

P
PaiChung22-Sapphire I
22-Sapphire I
May 2, 2022

When you say 'not able to import' do you get a failure message?

Or are you trying to 'reset' the data in the datatable?

If the second scenario, have you tried to 'purge' the entries from the DataTable before importing again?

A
AP_958723617-PeridotAuthor
17-Peridot
May 2, 2022

No. I tried to import the datas using same file in another new server. It showed logs as Skipped Import.

P
PaiChung22-Sapphire I
22-Sapphire I
May 2, 2022

Is it perhaps importing in the wrong order? i.e. the actual DataTable doesn't yet exist so it can't import the data?

Have you tried just importing the datatable data content after you've imported the entities?

W
wcui16-Pearl
16-Pearl
May 26, 2022

As we can not reproduce the same issue, can you reproduce it and make a short video so we can better understand it? 

V
VladimirRosu_11662719-Tanzanite
19-Tanzanite
May 26, 2022

Hi @AP_9587236 

 

What you experienced here is the default behavior when importing (at least) DataTables.

The reason is the following: when you export a DataTable, it generates just two files in the folder, a twx (contains data) and a chk (some sort of hash I presume).

The first time you import such a folder, ThingWorx generates an additional .import.log file, which, if you imported successfully the data, attests the import process finished successfully. Subsequent attempts to import check this file, and basically skips the data import if you already imported it once (data import can be quite intensive, and this is meant to be an optimization feature).

To bypass this functionality simply delete the .import.log file from the specific File Repository path and retry the import.

 

Terms & ConditionsAccessibility statement