Hi,
I am checking the new Rollbase 3.0 on hosted cloud and I am trying to link two OE service objects.
If the objects are created using the same catalog (two temp-tables related in one dataset) the relation is created and works ok. Creating the objects with two separate catalog files and trying to create the relation using 'New OpenEdge Relationship' raises an error
"Error: Types of selected PK and FK do not match"
The structure of the objects is:
objA: AId
objB: BId AId
The relation is made from objB to objA and the foreign key selected is AId (which has the same name and type as AId in objA).
Thank you.
Hi,
This error is shown when AId of objA and AId of objB are of different datatype.
For creating relationship between OESO created using different catalog, FK of objB should be of the same datatype as PK of objA.
Thanks,
Sopna.
Hi Sopna,
In the example above both fields are character.
WRT
> If the objects are created using the same catalog (two temp-tables related in one dataset)
> the relation is created and works ok. Creating the objects with two separate catalog files
> and trying to create the relation using 'New OpenEdge Relationship' raises an error
Hi Bill,
This is the scenario I am following:
objA is created from datasetA which contains only temptableA
objB is created from datasetB which contains only temptableB
The relation I want to create is 1-N between these two objects. The first example was using the two temp-tables in one dataset with defined relation in the dataset which works ok. For the second example I splitted the dataset into two datasets with one temp-table.
>> objA is created from datasetA which contains only temptableA
>> objB is created from datasetB which contains only temptableB
>> The relation I want to create is 1-N between these two objects.
Thank you for the answer. The problem appears when the PK field of objA is defined as Record Name as well. The datatype in Rollbase in this case is not 'Text' but 'Record Name'.
Selecting a different field as record name when creating the object solves this problem.
>> The problem appears when the PK field of objA is defined as Record Name as well.
>>The datatype in Rollbase in this case is not 'Text' but 'Record Name'.
Thanks for checking on what the issue is. This may be a ‘usage pattern’ that was not considered when the feature was added. Having the primary key as the Record Name is something that I think should work. This might be a good enhancement to consider.