Kbase P148319: Doc: setForeignFields error in OpenEdge Development: ADM and SmartObjects.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
22/06/2009 |
|
Status: Unverified
SYMPTOM(s):
Doc: setForeignFields error in OpenEdge Development: ADM and SmartObjects.
Syntax error in code of "SmartLinks > Invoking behavior in other linked objects > Pass-through links > Example of setting up a pass-through link"
Using the syntax included in the example causes getForeignValues to return nothing:
DYNAMIC-FUNCTION(?setForeignFields? IN h_dorder /* Order SmartDataObject
handle */ ,"Order.Cust-num, Cust-Num").
FACT(s) (Environment):
Windows
OpenEdge 10.x
CAUSE:
Bug# OE00136075
CAUSE:
Syntax error in the sample code. There is a space character after the comma in the "Order.Cust-num, Cust-Num" parameter passed to the setForeignFields function which expects a comma separated paired list of database table fields and the RowObject fields they map to.
FIX:
The OpenEdge Development: ADM and SmartObjects manual is a mature product and is no longer open for edits.
When using the setForeignFields function, ensure that there are no blank spaces before or after the comma in the comma separated paired list of fields.
The following examples are variations of the correct syntax of calling the setForeignFields function:
DYNAMIC-FUNCTION(?setForeignFields? IN h_dorder /* Order SmartDataObject
handle */ ,"Order.Cust-num,Cust-Num").
or
DYNAMIC-FUNCTION(?setForeignFields? IN h_dorder /* Order SmartDataObject
handle */ ,"Cust-num,Cust-Num").
or
DYNAMIC-FUNCTION(?setForeignFields? IN h_dorder /* Order SmartDataObject
handle */ ,"Order.Cust-num,RowObject.Cust-Num").