Review Import

Referring to someone else model on how the import was done to confirm the mapping - is it possible when you pick up a random model to review how the import was done?

Accepted answers

JaredDolich

@SatyamArora

I really like this question. If you do any work with a data hub this is a major challenge!

First, I agree with @Akhtar.shahbaz - these are really helpful insights.

As for best practices, I would like to reiterate my comment about documentation though because using IDS is really challenging when there are a lot of actions to search through.

Every time you create an action, determine immediately if this is an action that needs to be saved and/or reused. If it's not, clean it up be removing it.
If you decide to keep it I suggest you do the following:
1. Rename the action to something meaningful. If it's one step in a process give it a number so you can remember which step it's supposed to be.
2. Use the notes section to document what the action does. If it's an import action (model to model), make sure you document the workspace, model, and saved view you used. This will save you a the trouble of finding it in IDS.
3. If the import action is from an external source, again document the source and the name of the source so you can find it later.

Here's an example:

All comments

JaredDolich

@SatyamArora

Take a look at the import data source. You'll have to search for it though.

Beyond that, and as a personal best practice, I always document the source of the import in the description notes.

Lots of ideas suggested on this topic too on the idea exchange.

SatyamArora

Where can I find import data source? Are you referring to the files?

Let say they have been deleted.

Akhtar.shahbaz

Hi @SatyamArora

Go to setting tab -> Actions - > Import or Import data source

** You can only see the import mapping if workspace admin have given "Admin" or "Everybody" access to the upload file but still you can able to see the file name in data import source.

If it is model to model import then data imported through save view so you can see the source view name and target detail under "Import" option

Admin can delete the actions when they are not in used. If any action added to the process then if admin try to delete they will get pop-up message can't delete action this used in the process.

Hope this helps

Thanks

Akhtar

JaredDolich

@SatyamArora

I really like this question. If you do any work with a data hub this is a major challenge!

First, I agree with @Akhtar.shahbaz - these are really helpful insights.

As for best practices, I would like to reiterate my comment about documentation though because using IDS is really challenging when there are a lot of actions to search through.

Every time you create an action, determine immediately if this is an action that needs to be saved and/or reused. If it's not, clean it up be removing it.
If you decide to keep it I suggest you do the following:
1. Rename the action to something meaningful. If it's one step in a process give it a number so you can remember which step it's supposed to be.
2. Use the notes section to document what the action does. If it's an import action (model to model), make sure you document the workspace, model, and saved view you used. This will save you a the trouble of finding it in IDS.
3. If the import action is from an external source, again document the source and the name of the source so you can find it later.

Here's an example:

Quick Links

Can you help?

Unanswered questions

ADO Certification - Cannot Create Migration Link
Hi - I cannot seem to create a migration for Assignment 3 and it will not allow me to update the hierarchy and proceed further. It seems to think that a link has already been created, but I don't see anything. Any ideas?
How can i export accuracy metrics from Anaplan Forecaster to Model.
There was an error rendering this rich post.
A reminder of Bulk Copy - Current year to Prior year version for YoY analysis
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…