Error: There was a problem importing NPS Component Library. One or more component behaviour properties have a mismatched return type

[gionps]

Hi All,

Wondering if someone can help with the below issue, I made a minor change to my component library that was unrelated to any of my output functions or behaviour properties and I am now met with this error when trying to update the component in the app. Even if I delete all current versions of the components in the app, I get the same response! 

Thanks in advance!

Gio

[TheHole]

Hi Gio. I feel your pain! I've not done much with components to date, and I've been having this issue (or at least something very similar) today while playing around with the experimental custom 'Event' property. Very frustrating, but I may have a solution for you. Here's the problem I was facing . . .

I'd created a custom Event property containing several colour parameters and called it, SetTheme. I initially chose Record as SetTheme's Return Data Type, because it would churn out a record containing the selected theme colours, e.g., MenuFill, DefaultTextColour, etc. This worked well in the component studio, where I was able to pass my colours into SetTheme from a gallery, and then use the output to format several controls elsewhere; however, when I tried to import the component into a canvas app I got the same error as you. 

I fixed it by changing SetTheme's Return Data Type from Record to Text. Felt slightly wrong to do this, but the output still came out as a record variable, and it all worked perfectly.

Not sure I understand why Record didn't work, but this is an experimental feature, so that might have something to do with it. Or perhaps someone smarter than me may be able to explain?

So, double check that all your output properties have the correct Return Data Type and if you're using Record try using Text instead. (By the way, I'd also tried switching to a table and then referencing the first (and only) row – again, this worked fine in the component library, but I still couldn't import it elsewhere.)

One more thing to check . . . If like me you were trying to use an Event (or Action) custom property, make sure you have 'Enhanced component properties' switched on in your app's settings. You'll find it under Upcoming features > Experimental.

No idea if any of that contains the answer you're looking for, but I hope it helps! Good luck 👍

[sst_phat]

Hi all, we are facing the same problem in various tenants. The problem occurs in all component libraries, even if no changes have been made to them for weeks. Updates for the PowerApps portal have been rolled out in the affected tenants since last week. 

For us, the error behaves as follows: If the component libraries have already been imported into an app, updates can be imported without any problems. If the libraries have never been imported into the app, the error occurs.

There are a few components that have custom properties of the type "Event". We have checked all of them and have not found any mismatching data types. Unfortunately, even the workaround of changing the data types to "Text" did not solve the problem.

[gionps]

Hi TheHole,

Thanks for your reply, I have tested this out and sadly no luck! Appreciate the help though, thank you!

[gionps]

Hi sst_phat,

 Thanks for your reply, is this still an ongoing issue then. Does importing it post using the component library fix the problem?

Thanks 

[sst_phat · Accepted solution]

Hi gionps,

We have found a first workaround for the problem.

In the settings of the PowerApp, where you cannot import the components, two settings must be activated:

1. experimental > Enhanced component properties
2. retired > Disable component behavior property return type check

Then save the app and reload the page.

The import then works again. The return types also appear to be correct.

[gionps]

Hi sst_phat,

Awesome, it worked! Thank you for your help!