On-Premise Gateway is able to access the folder and name is coming up there in on-premise gateway as shown in attached screenshots in my description of the issue in the last comment.
Also I have used TestConnection code as well according to the given template by you. Still i don't see this connection type in the LOV when i try to create connection through this gateway.
So i have created .mez file through Visual Studio 2019. I have three parameters in my code URL, token and body. So in VS, when i execute my code, In the credential section i can see some characters which are getting added in the url section. For example, If I will pass "https://www.google.com/results" as url, in the datasourcepath field, it shows it as url: "https:\/\/www.google.com\/results",token:"passed token",body:"passed body". This is how it is building the datasourcepath field. So before every "/" VS is adding up one "\" I don't know why it is happening, may be VS is handling this special character escaping differently. not sure. This seems to be an issue as url is getting changed to something else. Please help on this.
Another potential issue could be datasourcepath should come as AOT but its taking the concatenation of all the inputs passed. For example url: "passed url",token: "passed token", body:"passed body" . So We do not create this DataSourcePath field anywhere in the code logic. So how this DataSourcePath field is getting created internally through VS. This is my another question. Please help on this as soon as possible.
Regards,
Yuga
