Loading
Feature degradation | Gmail Email delivery failureRead More
Visual Studio Code Based Modeler for Consumer Goods Cloud
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Standard Format

          Standard Format

          Use the standard format for all new datasource contracts. To use the standard format, set the external attribute in the <DataSource> tag to False.

          Required Editions

          Available in: Enterprise, Performance, and Unlimited Editions

          These element descriptions reflect the structure and attributes of the underlying XML.

          <!-- Each data source has a name that acts as a unique identifier.-->
          <DataSource Name="DsBoCall" businessObjectClass="BoCall" external="False" editableEntity="ClbMain" schemaVersion="2.0">
          <!-- Each data source has a number of attributes used for selecting columns.-->
           <Attributes>
          <!--Each attribute has a name that acts as a unique identifier, the name of the table of the attribute as well as the corresponding column of the table.-->
              <Attribute name="PKey" table="ClbMain" column="PKey" />
              <Attribute name="BpaMainPKey" table="ClbMain" column="BpaMainPKey" />
              <Attribute name="VisitType" table="ClbMeta" column="MetaType" />
              <DerivedAttribute name="isChanged" Type="Boolean" value="False" />
              <Attribute name="Longitude" table="SysLocation" column="Longitude" />
              <Attribute name="Latitude" table="SysLocation" column="Latitude" />
           </Attributes>
          
          <!-- Each data source has a number of entities used for selecting tables.-->
           <Entities>
          <!--Each entity is a table having a name that acts as a unique identifier and might have an alias, too. Additionally the primary table has an idAttribute. →
              <Entity name="ClbMain" alias="" idAttribute="PKey"/>
              <Entity name="ClbMeta" alias="">
          <!--An entity that has no idAttribute needs to have a join-statement.-->
                <Join Type="inner">
          <!--Join statements could either be defined as SimpleJoin or ComplexJoin.-->
                  <SimpleJoin>
          <!--A SimpleJoin has a number of simple conditions.There are different comparators which can be used in these conditions:
          "eq" (equal), ==
          "ne" (not equal), <>
          "lt" (lower than), <
          "le" (lower or equal), <=
          "gt" (greater than), >
          "ge" (greater or equal), >=
          -->
                    <Condition leftSideValue="ClbMain.ClbMetaPKey" comparator="eq" rightSideType="Attribute" rightSideValue="ClbMeta.PKey"/>
                    <Condition leftSideValue="ClbMeta.SalesOrg" comparator="eq" rightSideType="Parameter" rightSideValue="#SalesOrg#"/>
                  </SimpleJoin>
          <!--A ComplexJoin defines the join-statement directly as a text.-->
                  <ComplexJoin><![CDATA[
                   ClbMain.ClbMetaPKey =ClbMeta.PKey
                  ]]></ComplexJoin>
                </Join>
              </Entity>
                <Entity name="SysLocation" alias ="">
                  <Join Type="left outer">
                  <ComplexJoin><![CDATA[
                    ClbMain.PKey =SysLocation.ReferencePKey
                  ]]></ComplexJoin>
                </Join>
              </Entity>
           </Entities>
          <!--A data source could also have some QueryConditions which are directly defined as a text.-->
           <QueryCondition><![CDATA[
            ClbMain.PKey = #callPKey#
           ]]></QueryCondition>
          <!-- A data source could have some OrderCriteria.-->
           <OrderCriteria>
          <!--OrderCriteria contains a number of OrderCriterions. Each OrderCriterion has an Entity (table), an attribute which has to be defined as an attribute, as well as the direction of ordering (e.g. ASC =Ascending). →
              <OrderCriterion entity="ClbMeta" attribute="VisitType" direction="ASC"/>
              <OrderCriterion entity="SysLocation" attribute="Longitude" direction="DESC"/>
           </OrderCriteria>
           <Parameters>
              <Parameter name="callPKey" type="TEXT"/>
           </Parameters>
          </Datasource>
           
          Loading
          Salesforce Help | Article