Virtual PCF Dataset Component Not Getting Update

[sheldoncopper73]

Hello,

I have started working on the Virtual PCF dataset control by creating a sample component and pushed it in my CRM environment.

But, I recognized that whenever I make any change in the code and push it in my CRM, it doesn't reflect the latest change and always shows the code of the first push.

However, I did some troubleshooting and discovered that the code gets updated in the virtual field component and not in the virtual dataset component.

To confirm the above, I have created two sample components (one field and one dataset) and then updated both controls. The field component got updated while the dataset did not.

Is there a way to update the code in virtual dataset control?

Thanks!

[DianaBirkelbach]

Hi @sheldoncopper73 , 

This is interesting. I've struggled a lot last days with something similar.

I have a PCF which I use inside the Power Apps Grid control. My updates to the PCF wasn't applied, but I could see in the Solution Layers that the PCF was updated.

The only way I could work arround this: "Publish All Customizations", and then wait a little. When I could see the Notification banner, that there is a new App version, usually I could see PCF the changes in the Power App Grid  too.

I'm pretty sure, this wasn't like that about one month ago.

So maybe "publish all" will help you too work arround your issue too.

[a33ik]

@DianaBirkelbach what PCF CLI are you on? I noticed the similar behavior when I updated to 1.17.5 version. I rolled back to 1.16.6 and everything works fine again.

[sheldoncopper73]

Thanks @a33ik rolling back to 1.16.6 did the work!

[a33ik]

Hello,

If my reply (or replies) answers your question take a minute and verify the answer. You can do it by clicking "Yes" at the top of the reply (or replies) under the label "Does this answer your question?"

[DianaBirkelbach]

Thank you @a33ik ,

I didn't think it's because of the pac cli. I need to check with the version 1.18.4 which is out now.

[skoofy5]

We've found the same issue with the "latest pac install". I've made a comment in another thread earlier that our only workaround was to roll back to version 1.16 (https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/PCF-control-update-and-versioning/m-p/171...).

[DianaBirkelbach · Accepted solution]

Hi @sheldoncopper73 , @skoofy5 , @a33ik ,

The pac cli version 1.19.4 (current) fixes the issue. It was actually about not publishing after the import.

@sheldoncopper73 : can you please confirm if this solved your issue