This article describes common settings for all data sources in Meisterplan.
- Import Rules
- Sorting and Editability of Projects
- Own and All
- Update Behavior
- Delete Behavior
- Relation Rules
Use Import Rules to define update and deletion behavior during the import.
Sorting and Editability of Projects
The following options are selected for new data sources by default.
The Sort project list by priority of the imported projects option is available when projects are imported (Project with Properties is selected under Entity). Select this to update project ranks in Meisterplan during the import according to the Priority field of imported projects in the connected data source. The project with the lowest priority value will be ranked highest. When several projects are tied for the same priority, their ranking will be determined by the alphabetical order of project names. Selecting this option will also affect the positions of the must-have and cut-off lines.
Set Allow editing of global project data and deleting of imported projects in Meisterplan to allow users to edit global fields of projects imported from this data source and to delete such projects. The start and finish dates as well as allocations, milestones, dependencies and financials of imported projects can still be edited in Meisterplan even if this option is not selected.
Select the data types to import under Entity.
Please note that when you deselect Project with Properties but have already imported projects from this data source, importing any of the project detail data displayed indented under Project with Properties (Allocations, Milestones and/or Financials) may change the start and end dates of the projects they belong to if this is required to include the imported allocations, milestones and/or financials.
For each type of data selected under Entity, select the desired Update and Delete behavior when importing data.
The Update behavior determines how to treat data objects that are present both in Meisterplan and in your import source:
- All: overwrite any data objects of this type in Meisterplan that are also present in your import source regardless of their Data Source value in Meisterplan. The Data Source value of all objects overwritten in the process will be set to your import source.
- Own: overwrite data objects of this type in Meisterplan that are also present in your import source only if their Data Source value equals the import source.
- None: don't overwrite data objects of this type in Meisterplan, regardless of whether they are also present in your import source.
The Delete behavior determines how to treat data objects that are present in Meisterplan but not in your import source:
- All: delete any data objects of this type that are present in Meisterplan but not in your import source regardless of their Data Source value in Meisterplan.
- Own: delete data objects of this type that are present in Meisterplan but not in your import source only if their Data Source value equals the import source.
- None: don't delete data objects of this type in Meisterplan, regardless of whether they are also present in your import source.
Own and All
Each project is basically identified by its unique Project ID. Also each project has a Data Source entry which you can see in the project hint. The Data Source entry shows the original data source for each project. When you import a project via a Microsoft Excel data source, the data source name (e.g. "Excel") will be displayed. When you import a project from Excel via the main menu or create a new project in Meisterplan, the Data Source entry will be "Meisterplan". But the Data Source entry can change. This happens if you allow to edit imported projects in Meisterplan. When global attributes of an imported project are edited in Meisterplan, its Data Source entry will be changed to "Meisterplan". Also, if you import projects via a data source and set the Update behavior to All, the Data Source entry will show the name of the last data source from which the project was updated.
The behavior described for the project is the same for all other entities.
|Entity ID||Entity Data Source||Update||Result|
|Entity ID exists in data source||Current data source||Own||Update|
|Entity ID exists in data source||Current data source||All||
|Entity ID exists in data source||Other data source||Own||No update|
|Entity ID exists in data source||Other data source||All||Update|
|Entity ID does not exist in data source||Any entry||Own||No update|
|Entity ID does not exist in data source||Any entry||All||No update|
|Entity ID||Entity Data Source||Delete||Result|
|Entity ID does not exist in data source||Current data source||Own||Delete|
|Entity ID does not exist in data source||Current data source||All||
|Entity ID does not exist in data source||Other data source||Own||Not deleted|
|Entity ID does not exist in data source||Other data source||All||Delete|
|Entity ID exists in data source||Any entry||
|Entity ID exists in data source||Any entry||All||Not deleted|
Use Relation Rules to specify the ID mapping between entities from different data sources.
This can be used if different data sources are using different attributes for the unique identifier.