Skip to main content

Notifications

Power Automate - Using Connectors
Answered

Custom Connector and data type issue dropping trailing zero

(1) ShareShare
ReportReport
Posted on by 103

I created a custom connector to be used in a PowerApp that connects to an API that takes the following parameter (as a query in the URL):

sv=1.0

The data type is an integer and when I put the default value in for the parameter and test it, the value is input is getting changed to 1

If I run the test for the connector as 1 I receive an authorization failure. If I change the value from 1 to 1.0 on the test screen for that parameter it executes the test successfully. 

Thinking it is no big deal I saved the connector and added it to a PowerApp to test. PowerApps has the same behavior as I specify 1.0 as the value for the integer and it strips it back to 1 and I receive an authorization failure. I even tried formatting the number as Text(1,"0.0") which shows 1.0 but comes across as a string rather than text. If I further try this Value(Text(1,"0.0")) it comes out a just 1.


I would really like to fix this upstream (in the custom connector) to not have to deal with it in the PowerApp but am at a loss. Is this a browser behavior "helping" me by stripping the decimal off the 1.0 when I go from one screen to another? Anyone have any ideas?

 

Thanks,

 

Brian

  • parasrajput Profile Picture
    parasrajput 3 on at
    Re: Custom Connector and data type issue dropping trailing zero

    Got policy, 

    name: <anything you want>

    Template: override query string parameter

    Query parameter name: sv

    query parameter value: 1.0

    Action: override

  • Re: Custom Connector and data type issue dropping trailing zero

    Hello @BrianCCampbell,

    can you please provide the reference how we can create the policy to overrode the value query parameter.

     

  • Verified answer
    BrianCCampbell Profile Picture
    BrianCCampbell 103 on at
    Re: Custom Connector and data type issue dropping trailing zero

    I found a solution. There is a policy section on the left-hand side of the screen (Actions,Triggers,References,Policies) and there I was able to create a policy that overrode the value query parameter. Not really sure why it worked there but not in the default of the parameter - but I will take it! 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Microsoft Kickstarter Events…

Register for Microsoft Kickstarter Events…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Announcing Forum Attachment Improvements!

We're excited to announce that attachments for replies in forums and improved…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 145,666

#2
RandyHayes Profile Picture

RandyHayes 76,287

#3
Pstork1 Profile Picture

Pstork1 64,996

Leaderboard

Featured topics