Unable to persist the profile – Quick Tip

Hi Folks,

Are you debugging the Dynamics 365 Plugins using Plugin Profiler, did you ever notice this problem that you were unable to persist profile so as to debug your plugin. Did you got frustrated as you couldn’t capture the profile even after lot of tries installing and uninstalling the profiler. Just read on. I am writing this blog post after fixing a similar situation with one of my Plugin.

First of all, I would advise you to check the below.

  1. Plugin trace log under Settings –> Plugin Trace Log.
  2. Check if your Plugin is being called multiple number of times
  3. Check the filtering attributes of your Plugin whether it is causing to go in an infinite loop
  4. Suppose if you have added an image, did you select the respective attributes of the image
  5. Did you add sufficient depth conditions to prevent infinite loop executions.
  6. At what step is your plugin running, is it in PreOperation, PostOperation.? In case you were throwing an error, change it to Prevalidation step and check.
  7. Were you using persist to entity option while debugging, try changing to throw an error and see.
  8. If you note that the system becomes unresponsive and you were not able to download the log file, then definitely your logic is getting called multiple times. Please reverify.

Once you have verified these, you should be able to find out the exact root cause of the issue…I will leave to yourself.

Thank you…and enjoy debugging…Power Platform Solutions…

Cheers,

PMDY

Your Visual Studio doesn’t respond when opening Dataflow tasks in SSIS Packages in your local development machine? – Quick Tip

Hi Folks,

Thank you for visiting my blog today, this is another post talking about SSIS Data Flow Task which I encountered while performing data loading tasks using SSIS and would like to share with everyone.

Did your Visual Studio keeps not responding when you were opening the dataflow tasks for the SSIS Packages you or your team created as shown in image below. And you always try to close the same from task bar since you can’t work and keeps you frustrating, then this tip is absolutely for you.

The problem is actually with your Connection Manager, in your data flow task, you might have OLE DB Connections which the package is using in order to write information if there were any failures in the Data flow. In my case, I was actually writing to a SQL Table using a OLE DB Destination component.

If you cross check that SQL server availability, you should see the SQL Server (Your Instance) is stopped when you check in Start–> Services in the PC. In my case, I was using SQL Server (SQLEXPRESS01) in the SSIS Package as below.

And hence the SQL Server service is in stopped mode, the Visual Studio is not able to acquire the connection to open the package. You were almost there..

Just Start the service which you were using and voila…. your Visual Studio should open normally.

Thank you for reading….

Cheers,

PMDY