powered by CADENAS

Manual

Manual

3.3.1.6. Attribute mapping

The configuration is performed under %CADENAS_SETUP%\ifagile.cfg.

In this section you should not perform any changes normally. It just references to the next two sections.

[AttributeMapping(is3d)]
Attr_Content_00 =MAPPINGTOAGILE
Attr_Section_00 =
MAPPINGTOAGILE


Attr_Content_01 =LINKDB_RETURN_MAPPING
Attr_Section_01 =LINKDB_RETURN_MAPPING

Basics on attribute mapping are explained under Section 2.2.4, “Attribute mapping ”.

  • Return-Mapping: AGILE -> PARTsolutions PLINKDB

    In the section [LINKDB_RETURN_MAPPING(isRootDoc)] you can adjust, how and where the Agile attributes shall be transferred to the link database.

    Syntax:

    <TABLE>.<COLUMN>=?<VALUE>

    <TABLE> stands for "ERPTABLE" or "LINKTABLE".

    <COLUMN> stands for all columns excluding ERP_PDM_NUMBER.

    <VALUE> is the value on which the column <TABLE>.<COLUMN> is set.

    It can contain a placeholder like %MATNR%, which is set to the correct value by the PDM interface.

    Example:

    bla_%MATNR%_blub -> bla_12345_blub

    Supported placeholders:

    All valid, accessible AGILE database entries

    Example:

    T_DOC_DAT.DOCUMENT_ID

    For columns of the type "VARCHAR" the whole value expression <value> has to be embedded in single quotation marks (see following examples).[48]

    Example:

    [LINKDB_RETURN_MAPPING(isRootDoc)]
    ERPTABLE.MATNR=?"'%MATNR%'"
    ERPTABLE.SAPSTATUS=?"'%T_DOC_DAT.DOCUMENT_ID%'"
    ERPTABLE.TESTVC=?"'%T_DOC_DAT.C_ID%'"
    ERPTABLE.TESTINT=?"555"

  • Mapping: PARTsolutions PLINKDB -> AGILE

    In the section [MAPPINGTOAGILE] you can adjust, where PARTsolutions attributes (link database) (right side) have to be transferred to Agile (left side).

    [MAPPINGTOAGILE]
    T_DOC_DAT.DOC_NAME=NAME
    T_DOC_DAT.DOC_NAME_GER=NAME_DE
    T_DOC_DAT.DOC_NAME_ENG(isRootDoc)=?"NAME_EN"



[48] needed for correct SQL queries