In case this might be of use to someone later,
with the help of a colleague, I found the reason
for the type mismatch is that the parameter order
from a BPM/ABL for Configuration.GetConfigurationSequence
is different from what the XML file says (I also had to
add OUTPUT for the last parameter). The order actually is:
Order Direction Name Type
1 INPUT ConfigMode CHARACTER
2 INPUT RelatedToFile CHARACTER
3 INPUT RelatedType CHARACTER
4 INPUT LinkKey1 CHARACTER
5 INPUT LinkKey2 CHARACTER
6 INPUT LinkKey3 CHARACTER
7 INPUT LinkKey4 CHARACTER
8 INPUT LinkKey5 CHARACTER
9 INPUT PartNum CHARACTER
10 INPUT RevisionNum CHARACTER
11 OUTPUT ConfigurationSequenceDataSet DATASET
12 OUTPUT nonApprvMessage CHARACTER
I got the proper signature through the "Advanced" button
in the Method Directive window for Configuration.
Somehow I thought the XML file made more sense but I was wrong.
Have a nice day,
Yves
with the help of a colleague, I found the reason
for the type mismatch is that the parameter order
from a BPM/ABL for Configuration.GetConfigurationSequence
is different from what the XML file says (I also had to
add OUTPUT for the last parameter). The order actually is:
Order Direction Name Type
1 INPUT ConfigMode CHARACTER
2 INPUT RelatedToFile CHARACTER
3 INPUT RelatedType CHARACTER
4 INPUT LinkKey1 CHARACTER
5 INPUT LinkKey2 CHARACTER
6 INPUT LinkKey3 CHARACTER
7 INPUT LinkKey4 CHARACTER
8 INPUT LinkKey5 CHARACTER
9 INPUT PartNum CHARACTER
10 INPUT RevisionNum CHARACTER
11 OUTPUT ConfigurationSequenceDataSet DATASET
12 OUTPUT nonApprvMessage CHARACTER
I got the proper signature through the "Advanced" button
in the Method Directive window for Configuration.
Somehow I thought the XML file made more sense but I was wrong.
Have a nice day,
Yves