bw:databuilder_tool

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
bw:databuilder_tool [2020/12/15 12:37]
akoehler [Create Main DataBuilder Step]
bw:databuilder_tool [2022/08/02 15:33] (current)
akoehler
Line 7: Line 7:
 The following documents contain additional information that may be helpful with the development of Bizweaver workflows. The following documents contain additional information that may be helpful with the development of Bizweaver workflows.
  
-  * **[[bw:web_service_tool|WebService Tool]]**+  * **[[bw2:web_service_tool|WebService Tool]]**
  
 ====== Before You Begin ====== ====== Before You Begin ======
Line 13: Line 13:
 You will need to know, or have examples of , the data structures the API is expecting. This includes element (field names) and child objects within the structure. Keep in mind that names will generally require an exact match, including case. You will need to know, or have examples of , the data structures the API is expecting. This includes element (field names) and child objects within the structure. Keep in mind that names will generally require an exact match, including case.
  
-====For SAP Business One Service Layer====+=====For SAP Business One Service Layer=====
 An easy way to view the data structures used for SAP Business One is to create a small workflow that executes a GET on the object in question.  The workflow will have two WebService2 steps: a login step and a GET step.  The GET step references the target object (e.g. SalesOrders). The GET step will return the data structure for the object in the "Output String."  This is also an easy way to create a template file for the object in your environment as it will include any user-defined fields as well. An easy way to view the data structures used for SAP Business One is to create a small workflow that executes a GET on the object in question.  The workflow will have two WebService2 steps: a login step and a GET step.  The GET step references the target object (e.g. SalesOrders). The GET step will return the data structure for the object in the "Output String."  This is also an easy way to create a template file for the object in your environment as it will include any user-defined fields as well.
  
 +More information dealing with SAP Service Layer can be found **[[bw2:sap_business_one_integration_using_service_layer|here]]**
 ====== General Notes ====== ====== General Notes ======
  
Line 124: Line 125:
  
 {{  :bw:databuilder6.png?600  |}} {{  :bw:databuilder6.png?600  |}}
 +
 +====Databuilder Variables====
 +^Name         ^ Description         
 +|AddAsArry|True or False if the add as array checkbox is selected|
 +|CumulativeData|This is the collection of all data that was built in the databuilder|
 +|Data|This is the last run of data that was entered into the databuilder|
 +|DataSourceName|This indicates the name of the tool that is being used for the source data for the databuilder|
 +|DataType|This indicates the type of data your are building XML or JSON|
 +|ObjectName|Is the name of the top level of your JSON or XML|
 +|TopLevelElement|True or False if the top level element checkbox is selected|
 +| StepMessage|During a failure the reason for failure will be populated here |
 +| StepStatus        |True or False|
  
bw/databuilder_tool.1608053863.txt.gz · Last modified: 2020/12/15 12:37 by akoehler