Hi all,
https://www.youtube.com/watch?v=XrWcPgEtxdo
Followed the above tutorial to learn a little bit about custom connectors and APIs. Ran into a huge problem with the custom connector dropping the leading zero in the API Request URL. I am really not sure what to do about this issue. It pretty much renders this or other Power app with a Leading Zero as a parameter useless.
How would one keep the leading zero when it is being added to a URL? Is this a a 'bigger' issue with Microsoft products?
Actions taken so far:
Adjusted the concatenate Variables to return as plaintext instead of the Value type. They are coming back with the leading Zero.
Set(varDunNumber, PlainText(Concatenate(tblCompanyList.Selected.duns, tblCompanyList.Selected.duns_plus4)));
Set(varCompanyResult, SAM.FindCompany(varDunNumber).sam_data.registration)
the formula bar shows carDunNumber = 0814668490000 [Image attached]
I have changed the source json to a string not a integer 'int32'. (no affect). Made the change in the 'Changed the Definition's Request Path Parameter Type ' while creating the custom connector.
Opened the Power App Monitor to troubleshoot
Request being sent changes the SAM.FindCompany API call request URL to below. Now the leading Zero is missing.
Response come back with an error "body": {
"Message": "Duns number must be 13 digit long",
"Error": "",
"Code": 406
