Unanswered

Plugin Assembly does not show up in Registration Tool

(0) Share

Report

Posted on by datapawn

I have inherited a big project from a former lead dev. I'm new to Powerapps and Dynamics, so I'm trying to sort out what to expect.

In the Plugin Registration Tool i can see 4 assemblies that are registered (both in XRM toolbox and it the MS Plugin Reigistration Tool, same Assemblies show up).

There are more than 4 assemblies in our git repo, and in a larger solution just called name.Dataverse.

I've modified the C# code in one plugin solution to include a new field we've added to the data, and I think I follow all of that okay. But why does the plugin not show up for me to Update it? Does this mean it's another form of automation (maybe Power Automate?) that's doing this, and the assembly i've inherited is not, in fact, registered and executing? Or can a Plugin be registered and functioning and not show up in the Registration Tool? If so, how do i modify it? Or what happens if i just... register it again?

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (1)

datapawn on at

Like (1)

Report

Just tested, and the code executes, but does not show up in System Jobs, either. The other Workflows and Plugins that affect the same table also work, but they also show up in the Registration Tool and in System Jobs.

Was this reply helpful? Yes No
Verified answer

Parvez Ghumra 1,579 Moderator on at

Like (1)

Report

@datapawn I'd suggest checking the properties of the Visual Studio plugins project - the compiled .NET assembly might be being assigned a different name compared to the Visual Studio project?

Also if the plugin is designed to run synchronously it will not show an entry in system jobs - so I'd suggest checking the plugin step configuration if it's meant to run synchronously or asynchronously.

Was this reply helpful? Yes No
datapawn on at

Like (1)

Report

Thank you! This lead me to search for what other ways you can see if code is executing, and found out about Trace Logs - and thankfully that helped me figure out that the changes i was making were, in fact, to deprecated code. So i did a thorough search throughout the whole solution and basically found the exact same functionality I'd been tasked with editing re-created in _another_ Plugin Assembly that _was_ installed and showing up in the Register.

After that I did have to rebuild the project as .NET 4.7.1 (I guess PowerApps doesn't use newest .NET?), but once I did that I could Update the Plugin as I've seen elsewhere. So i just closed the ticket with edits made! Thanks!

Was this reply helpful? Yes No