> For the complete documentation index, see [llms.txt](https://help.auxalia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.auxalia.com/plant-tools/de/plantlink/how-to-use/link-configurations/create-an-update-link.md).
# Aktualisierungslink erstellen
In diesem Kapitel wird die Verwendung von Update-Links beschrieben, die Daten aus einer Datenquelle in Plant 3D-Eigenschaften zuordnen/kopieren.
Ein Link zu dem in diesem Kapitel erstellten Projekt befindet sich am Ende dieses Kapitels.
In diesem Beispiel ist die Datenquelle eine einfache SQLite-Tabelle. Es können auch andere Datenquellen verwendet werden (siehe [SQL-Server verwenden](/plant-tools/de/plantlink/how-to-use/link-configurations/use-sql-server.md), [MS Access verwenden](/plant-tools/de/plantlink/how-to-use/link-configurations/use-ms-access.md), [MS Excel verwenden](/plant-tools/de/plantlink/how-to-use/link-configurations/use-ms-excel.md)). Die Plant 3D-Datenbanken können ebenfalls verwendet werden (siehe [Tag von verbundenen Objekten in Instrumente übertragen](/plant-tools/de/plantlink/how-to-use/use-cases/getting-tag-from-connected-objects-into-instruments.md)).
Beispieldaten und Umfang
Die Tabelle, die wir in diesem Beispiel verwenden, hat 5 Spalten. Die Spalte **rowid** wird standardmäßig angezeigt, ist jedoch nicht in der Tabelle vorhanden. Wir wollen die Daten aus den Spalten **ModelNo, Manufacturer, Price und Desc** in die P\&ID-Eigenschaften einbringen. Dieses Beispiel soll eine Art Ausrüstungskatalogdaten simulieren.
Einrichten der Linkkonfiguration
To setup a link configuration we need to open the main user interface of **PlantLink** from the **PlantTools** ribbon.
Next you click on **New\...** to create a new Link Configuration.
This opens the PlantLink Wizard. Since we are using an SQLite database you select **Data Source File:**. For all other data sources you have to use a UDL file. More about this under [Use SQL-Server](/plant-tools/de/plantlink/how-to-use/link-configurations/use-sql-server.md), [Use MS Access](/plant-tools/de/plantlink/how-to-use/link-configurations/use-ms-access.md), [Use MS Excel](/plant-tools/de/plantlink/how-to-use/link-configurations/use-ms-excel.md). Click on **Browse** to open the file selector.
In this example, the SQLite database is stored in the **Related Files** folder in our project.
After you click **Open** the Wizard checks if the path to the database file can be change to a relative path. This makes it easier in case you later want to copy the project. Then there is no need to adapt the Link Configuration.
We keep the default selection **Update AutoCAD P\&ID/Plant 3D properties**. The other options will be explained in the following chapters.
Since this table contains equipment catalog data, we select the **Equipment** class to map the data from the table to the equipment properties our P\&ID symbols.
You can select Tables and Views from the database file. But in this case there is just one table available.
Now we need to define the linked fields. This essentially tells PlantLink how to find suitable rows/datasets in the table. It more or less filters the table. In this example, we use the PIDType from the table. This contains P, W, and T (check with the first image above).
There are some standard Conditions available. We select **= Equals**, because the type of the equipment symbol is used to filter for PIDType in the table.
Select Type which contains the selection list with the various equipment types in our equipment symbols. The option **Show warning box if no suitable datasets can be found** opens a warning dialog informing you, that PlantLink couldn't find anything based on the linked column/property. **Show only suitable datasets when using 'Assign Data'** later limits the presented rows/datasets to only the ones where the linked columns/properties meet the set conditions. Otherwise the **PlantLink - External Database Viewer** will show all rows/datasets from the table.
Next we define the columns from the table and map them to PID properties. The order of the mapping defines the order of the columns when there are multiple choices. The option **Behaviour for multiple records** controls what should happen, if there are more than one suitable rows/datasets. The default setting is **Ask User**. In this case the **PlantLink - External Database Viewer** dialog will show up and the user selects the correct row/dataset. When using **Select first matching record** PlantLink will just use the first of the found candidates from the table.
You select the column and the class property to which the columns should be mapped. The option **Write back** allows you to later edit the mapped values and have them written back into the table (see [Mapping Options](/plant-tools/de/plantlink/how-to-use/usage/mapping-options.md)). The option **Clear Value** deleted an existing value in case PlantLink cannot find a suitable row/dataset (see [Mapping Options](/plant-tools/de/plantlink/how-to-use/usage/mapping-options.md)). The option **Override Acquisition Mode** can change the acquisition to manual in case the property you map to has an acquisition rule (see [Mapping Options](/plant-tools/de/plantlink/how-to-use/usage/mapping-options.md)).
For **Sync Mode** we use **On drawing save**. This ensures, that the mapping for those properties will be refreshed when the drawing is saved, or closed and saved. So when you close and save your drawing, your mapped properties are up-to-date. More details about **Sync Mode** can be found under [Mapping Options](/plant-tools/de/plantlink/how-to-use/usage/mapping-options.md).
Finally, we select **Price** for which there is no PID property available.
Therefore, we can have PlantLink create a **New Property...** without the need of entering Project Setup ourselves and create the property. The property will be created for the selected class in the Wizard.
A dialog will appear where you enter the property name and display name. And whether the property should be **Visible** and/or **Read-Only**.
We type in the following values.
We see an \* in front of the property indicating a new property.
Lastly, we define the name of the Link Configuration. The option **Use this Link Configuration in PlantDataManager** tells PlantDataManager if this Link Configuration can also be used in PlantDataManager.
We now see the Link Configuration in the main dialog of PlantLink and it shows **Active**. The Link Configuration appearing in alphabetical order. This can become important when Link Configurations depend on each other and must be executed in a certain order (see [Rename, Edit, Delete, Deactivate Link Configurations](/plant-tools/de/plantlink/how-to-use/usage.md)).
Testen der Linkkonfiguration
Wenn wir jetzt im Projekt-Setup ein Pumpensymbol einfügen, das P als Standardwert hat, erscheint der **PlantLink - External Database Viewer** und bietet die beiden Auswahlmöglichkeiten für PID Type=P. Wir verwenden zum Beispiel die erste Reihe.
Danach erscheint der Dialog **Tag zuweisen**, in dem Sie wie gewohnt Ihr Tag definieren.
Wenn wir uns die Eigenschaften ansehen, sehen wir **Modellnummer, Hersteller, Beschreibung und Preis**. Für die Bilder haben wir die **PlantExpressTools PropertiesPalette** konfiguriert (siehe [Properties Palette](/plant-tools/de/plantexpresstools/collaboration-workflows/propertiespalette.md)).
Beim Einfügen eines Wärmetauschersymbols erscheint erneut der **PlantLink - External Database Viewer**. Wir wählen erneut die erste Zeile aus.
Und wir sehen die zugeordneten Daten in den Eigenschaften.
Beim Einfügen eines Tanksymbols wird jedoch kein **PlantLink - External Database Viewer** angezeigt, aber wir sehen die zugeordneten Werte. Dies liegt daran, dass es in der Tabelle nur eine Zeile für PIDType=K gibt.
Weitere Einzelheiten zum Ändern und Auswählen zugeordneter Daten finden Sie unter \[Andere Zeile aus Quelle auswählen] (pl\_htu\_usage\_001.md).
{% file src="/files/b1v5ga7YmCcMMs5g30jI" %}