How to add URL parameters to a function import call in Action Project in SAP BPA

[rohit_singhal]

Hi All,

Greetings of the day!

I am facing a peculiar issue in using Function Imports from oData services in Actions Projects.

The scenario is as follows:

• Using Action Groups in automation to replace individual API calls being made previously.
• The action project has been created using a destination and an oData end point.
• A single Action Project created where Get, Post and Patch calls are working.
• Issue is in Function Imports for the same Action Project.

Issue Description:

1. On adding the function import, the URL parameters are listed in Body of the Input.

If I test using this, I get the error:

Invalid Function Import Parameter '<ParameterName>'

2. If I remove the keys from the Body, and manually add them in the parameters as query/header/path/custom

On testing this gives one of the two types of errors:

a. Invalid Function Import Parameter '<ParameterName>'

b. The call throws a javascript error in console log and the screen remains in busy mode.

Is there a way, in which I can introduce the URL parameters in the suffix, instead of adding these parameters through body/parameters?

How would I go about doing this.

Working custom web service call URL:

Action Project, looks issue:

Best Regards,

Rohit

[Dan_Wroblewski]

WHen you say add to suffix, what do you mean? Also did not understand how URL parameters could be in the body?

[rohit_singhal]

Hi Dan,

Thanks for your response.

That's exactly the issue. The URL parameters: DeliveryDocument and DeliveryDocumentItem should have ideally been visible in the action project as:

"/PutawayOneItem?DeliveryDocument='{DeliveryDocument}'&DeliveryDocumentItem='{DeliveryDocument}'"

However, the action shows only the suffix:

"/PutawayOneItem"

I wanted to know, how I could potentially update the suffix in the action to the above case.

This is how the import function looks like when added in the action project:

Best Regards,

Rohit

[rohit_singhal]

@Dan_Wroblewski

Hi Dan,

Do you have any insights on this? Any help would be greatly appreciated.

Thanks.

Best Regards,

Rohit

[rohit_singhal · Accepted solution]

Finally resolved the issue.

I removed the function import methods provided through the API manifest. I then added the same function imports using custom actions.

With this, I could add the URL parameters in the API call.

I just had to make all the relevant configuration in the Input fields.

Best Regards,

Rohit

[Dan_Wroblewski · Accepted solution]

With actions you can completely control the OData URL parameters, which means you can make use of alot of great OData functionality, whether v2 or v4 ... great that everything is working for you