|for Sage Data Exchange|
Define the columns to return on a request from your application in Return Maintenance, including the assignment of an alias. (If assigned, the alias will be used in all methods.)
Return columns are created for each Resource. (Resources are added in Resource Maintenance.) Select a Resource to maintain the Return columns.
Data Sources are links to the tables associated with the Resource. For Sage 100 Resources, the name of the Data Source for main table of a Resource is always "MAIN". If the Resource has an associated detail table, as in Sales Orders or Sales Invoice History, the Data Source is "DETAIL".
Other Data Sources are tables that are linked to the main or detail. For example, the Terms Code Description for a Customer is not in the main Customer table. You would find it in the linked TermsCode Data Source, linked by the Default Terms Code.
Select the Column Name to be returned. The default name of the column returned to your application is the column name in the Sage 100 table. (You can create an alias.) Any column can be returned, including Custom Office User Defined Fields and the columns in User Defined Tables linked to the Resource.
The default name of the column returned to your application can be aliased. The alias will be used in all methods.
Properties are separate classifications that can be created in any Resource, but it is predominantly used in the Products Resource.
Your application may want to limit the products being viewed by a property of the product. For example, your customer is viewing all the furniture you have in stock. To limit the list, they may choose to view only the furniture with a mahogany finish. In Sage Data Exchange, you would have a column for that Property that defines the finish of each piece of furniture. The column can be a Sage 100 Custom Field, like UDF_Finish. You would probably alias the column to "Finish".
Table Name (Read Only)
Table Name is just a reference to the table in Sage 100.
Column Type (Read Only)
Stings and numerics need to be handled differently.
If your application is returning a list, you may not want every column returned in the list. However, when requesting detail on a single entity (i.e. one Customer), all columns should be returned. This flag helps cut down on unnecessary network traffic.