CUSTOM CONNECTORS: Hiding API Key and Other Parameters Not Working?

[ericonline]

So... I'm fairly certain I've created Custom Connectors in the past where:

• I've edited a Request Parameter
• Entered a Default value
• Marked it as Internal
• Then its not required in the Custom Connector Function in the PowerApp

Why is this no longer working?

Example:

• API-Version Default value entered
• Marked as internal
• 
• API-Version shows "grayed out" in the CC Test Area
• 
• BUT
• Still shows required in the actual PowerApp
• 

Troubleshooting so far: 

• Updated Connector
• Removed/readded/ the Custom Connector from/to the App
• Saved/closed/reopened the app. No change...

Why? Thoughts?

[DavesTechTips · Accepted solution]

Hi @ericonline 

You seem to have followed the correct troubleshooting steps. The only thing that might cause this is the 'Is Required' setting which is set to no, that makes it optional and causes it to display on the front end. I agree that this doesn't completely make sense as you have specified a default, but it should do the trick.

You will have to readd the connection to the app, but from your troubleshooting steps I can see you have know this 😉

twitter: @dawidvh

youTube: https://www.youtube.com/user/dawidvanheerden

**If you found this reply helpful, please mark this as the answer to close the topic and make it easier to find for other people with similar questions. AND we get points for it 😉

[DavesTechTips]

Hi @ericonline 

Did this manage to solve the problem?

Have  a great day.

[ericonline]

Hi @DavesTechTips ! 

Thank you for the follow up and thank you for the solution. 

You were right. Once I marked those parameters as "Required", they were no longer needed in the Custom Connector. I did not have to remove / readd the Custom Connector, just open the app and the changes were active.

#PowerHomies!

[ericonline]

Hi @DavesTechTips ,

Weirdest thing. Today the Custom Connector is not working and is requiring "api-version" again... strange.

[ericonline]

Weird.. I cant explain why, but the query needed to be changed from THIS:

ClearCollect(
    colAPIResults1
        API.GETthing1(
            {
                'api-version': 1.0,
                query: varLatLong,
                'subscription-key': "123"
            }
        )
);

ClearCollect(
    colAPIResults2,
        API.GETthing2(
            {
                'api-version': 1.0,
                query: "THINGS",
                'subscription-key': "123",
                lat: varLat,
                lon: varLong
            }
        ).results
)

...TO this...

ClearCollect(
    colAPIResults1,
        API.GETthing1(
            "1.0",
                {query: varLatLong}
        )

);

ClearCollect(
    colAPIResults2,
        API.GETthing2(
            "1.0",
            20000,
            {query:"THINGS",lat:varLat,lon:varLong}
        ).results
)

Working now, but not sure why the change needed to occur 2-3 days later like this.. I haven't touched this connector since last week.