SamplePlugin | Bukkit Sample Plugin

The thing is, even when you're writing plug-in code in Python, you'll still be handling Vimscript events, accessing Vimscript variables, using Vimscript for mapping keys and so on. Writing plug-ins in Python essentially means writing them in Python and Vimscript.

You should use your main Python module (sample.py) to define functions rather than execute code at the top-level. Then you can use mappings or auto-commands to trigger those functions on specific events.

For example, to trigger compilation on pressing F5:

What's the use of passing configuration data to plugin and how to do this ?

Sometimes we may need to do configuration items just like connection strings or log settings in application development files, web.config or app.config. Similarly, You can pass this from the plugin step when you are registering using plugin registration tool.

The biggest difference that you’ll seen mentioned between these two settings is that the secure configuration is only viewable by CRM Administrators while the unsecure configuration is viewable by any CRM user. However, there’s another important difference: the unsecure config will automatically move between environments with your CRM solutions. This means that even a setting that you might consider fine to let any CRM user read like the URL of a website or settings to enable more verbose trace logging in a development environment might be more appropriate in the secure configuration if you want it to be different between environments. Otherwise, you have to worry about overriding the unsecure config setting in production with the value you have in your development environment every time you import a solution containing the plugin step.

Any real time scenario with example?

1. Web service credentials (secure)
2. Website URL that differs between environments (secure)
3. Log settings that you don’t want to move with a CRM solution (secure)
4. Template string that you’d want to move with a CRM solution (unsecure)
5. Constants that you’d want to move with a solution like “MaxRetries” or “NumberOfDaysToFollowUp” (unsecure)

Reference

In your plugin you are creating a new task 'sample' and set a constraint "sample must run after check": but this does not include the sample task in the task graph . It just says: "if sample and check tasks are both executed , then check task must be executed first". So if you just execute 'gradle build', this will not trigger execution of task "sample".

Try to execute directly "gradle sample" : you will see it will trigger its execution, and make the execution of "check" task first in respect of the contraint you have defined in plugin.

If you want to make "sample" task execute each time you execute "build" task, then just set a "dependsOn" constraint between "build" and "sample" tasks, in your plugin:

You unraveled some parts yourself, but there's a non-trivial part of JavaScript function trickery involved. Let's put them apart:

arguments is a “magic” variable inside function bodies, that offers access to the function arguments. It's simply there without declaration, and works like an array but is no array (will become important in a moment).

If you want to access the first argument to a function, arguments[0] is the place to look. In your specific function, that’s always identical to the variable method.

If you want to get any additional arguments (remember, that you can call JS functions with any number of arguments, not just the ones declared), a first pass might look like this:

I recommend you below steps:

1. Unregister the Plugin assembly & Profiler
2. Download latest 365 SDK
3. Register the assembly freshly using new PRT from latest SDK
4. Install Profiler & try again
5. Most important - The error log you shared cannot be used to debug using Profiler. It will be different

Your Plugin name is PostCreateAccount & checking context.OutputParameters.Contains("id") which means PK of just created Account.

But you are referring it to RegardingObjectId as Contact while creating task. And verifying in CRM contact record. Do an advanced find for tasks created & you can troubleshoot.

For consistency make sure of this - Your step name in PRT says “Update of Account”.

I do see PostCreateContact plugin in your screenshot, if you are playing around with code, verify all the changes you are making.

Update: By seeing your exception, this is coming from FieldService plugin which is installed per your trial subscription. If you are not using, You may remove the FieldService solution Or unregister the Assembly. Or Simply just disable the below Step in PRT.