Import AMEFF files directly into a workspace (aka business unit)

Gepland

Patrick Storms

9 augustus 2022 11:49

Problem

When uploading an AMEFF file, the objects are always created in the master business unit (workspace). There is no way to import directly into a designated workspace. As a consequence, you have to manually select the newly created objects and move them to the correct workspace. If the import or the master workspace contains many objects, this is a tedious task. Moreover, because there is no way to see which objects have just been created.

Wish

Option 1: Add a column 'import date' or 'import filename' to the object viewer. Make sure you can sort / filter on this column value. That way it is easier to select and move the newly created objects.

Option 2: Before the import starts, let the user select the correct workspace.

Impact

Strongly depends on (a) how often you need to import data from AMEFF and (b) how much data the file contains. This will not happen on a daily basis. However, it takes hours to fix a big import. Should be part of the So I would rank this wish as "3" on a scale of 1-5.

3

• 

  Tom de Ridder

  9 augustus 2022 12:01

  We need this. Moving imported objects and views right now to a workspace is tedious and almost impossible to detect what objects belong to what import. 

  Same thing goes for source processing altogether, but I do recognize if we me move away from data sources and move to just APIs for manipulating objects, we should be able to determine what workspace to create, edit or delete an object from.

  0
• 

  Koen van der Veldt

  10 oktober 2022 11:19

  The new and improved public API is on the roadmap and developed as we speak. 

  0

U moet u aanmelden om een opmerking te plaatsen.