Question
Computershare
US
Last activity: 10 Oct 2023 5:35 EDT
Dynanically generate the query string for a connect-rest rule.
We recently upgraded from 7.x to 8.x and are having issue with one of our connect rest rules. We have a bunch of different datapages that use the same connect rest rule but with different path and different sets of parameters for the querystring. Thus we are using the Request Data Transform in the rule to set the resource path to also include the querystring parameter and in 7.x we were able to send that directly to the connect rest rule with no problem. However with the changes to 8.x connect rest rule, now each parameter must be declared, which would cause us to have to write a separate connect rule for each datapage. We tried to continue using our methodology but now the IIS server we are contacting is giving us the following error: Server Error in '*************' Application. A potentially dangerous Request.Path value was detected from the client (?). Has anyone found a way around this?
Tekclan Software Solutions
IN
Hi @Max Toedtemeier,
In connect rest we are having option to skip resource path parameters and query string parameters. We can add multiple resource path and query string parameters in request data transform based on our requirement will skip parameters in request data transform.
Example 1: without value for resource path and query string parameters:
Example 2: passes some resource as param as empty and some resource as constant:
Hi @Max Toedtemeier,
In connect rest we are having option to skip resource path parameters and query string parameters. We can add multiple resource path and query string parameters in request data transform based on our requirement will skip parameters in request data transform.
Example 1: without value for resource path and query string parameters:
Example 2: passes some resource as param as empty and some resource as constant:
From the both examples we seen we can able to dynmically make decision about resource path and query string parameters.
Thanks,
Dhanasekar Chellamuthu
Computershare
US
@DhanasekarC0202 So in your example you still have to declare every distinct querystring parameter that can be passed in. Have you been able to leave the querystring open ended and dynamically generate in the map request rule of the datapage consuming the connect-rest?
Thanks,
Tekclan Software Solutions
IN
We can use application settings rule to skip querystring parameters configuration in rest rule, instead we can create separate date page to have all the possible url based on the requirement by passing parameters. and use that data page in Application settings rule, from request data transform you can set the value to static pa
1.Request data transform:
SamplePage.stringParam1 = "json"
2.Application setting Rule:
use URL Data page.propertyname
3.URL DataPage:
From SamplePAge.stringParam1 we can have conditions : so that we can form new url
In below screenshot i added only application settings rule configuration. After that we need to follow 1,2,3 steps.
Computershare
US
@DhanasekarC0202So are you storing the full string including query string parameters in the application settings?
Tekclan Software Solutions
IN
@Max Toedtemeier we can use application setting also otherwise we can input data page to get url.
Thanks.