Product Demo Videos

Your Power Platform Coding Assistant in Visual Studio

Welcome to our demo library of the Kupp Code Analytics!
Here you can easily find our demo and tutorial on how and why the tool is a perfect Visual Studio extension for all PowerPlatform and D365 developers

For more information, contact us at support@kuppsoft.com

Quickstart Guide

How to install the Kupp Code Analytics in Visual Studio 2022 and start having a better Power Platfom/D365 coding experience. 

[IntelliSense] Walk-through video part 1 (with voiceover & ENG subtitles)

In this demo, we will showcases a quick overview of 3 productivity features from Kupp Code Analytics.
 
💡 IntelliSense for plugin-related Metadata
💡 IntelliSense for Entity Relationships 
💡 IntelliSense for ActivityParties
 
What's in it for you?
Save up to 50% of your time on locating & fixing errors
Get instant code recommendation
Ensure best coding practices 

[IntelliSense] Walk-through video part 2 (with voiceover & ENG subtitles)

In this demo, we showcase another 4 common use cases of KCA's productivity feature (IntelliSense) that could save up to 50% of your coding time in Visual Studio
 
💡 The resolution of delegates: You have an Entity account and a basic delegate that returns to an Account entity. What if you want to access the attributes of this Account entity? KCA will instantly suggest all attributes from the entity "Account" for you. 

💡 OptionSet Value: these values always have tricky "magic number". In this example, if you want to get the OptionSet value from the Account entity, KCA will provide all possible values in the entity "Account," so you can easily compare and choose the correct one. 

💡 Context-specific Relationship: If you have the LinkEntity and this class takes five parameters that have a specific context for each other such as LinkFromEntityName, LinkToEntityName, LinkFromAttributeName, LinkToAttributeName. In this demo, the first Entity is Account, the second Entity is Contact. With KCA, you can see the first parameter - LinkFromAttributeName and all suggested attributes from the Account Entity, while the LinkToAttributeName will only suggest attributes from the "Contact" entity. 

💡 Constructor Properties: KCA also works with the constructor properties and suggests only relevant attributes in the chosen Entity. 
What's in it for you?
Save up to 50% of your time on locating & fixing errors
Get instant code recommendation
Ensure best coding practices 

 

[IntelliSense]: Detect Plugin Image Name

To identify the runtime image entity (Pre-Image / Post-Image), the plugin image data is retrieved. Furthermore, the entity is set to the plugin's context Pre- or Post-Image.

 

 

[IntelliSense]: Detect Entity from Target

To identify the runtime entity (Target), the plugin entity data is retrieved. Furthermore, the entity is set to the plugin's context target.

[IntelliSense]: Support for ActivityParties

In this case, the entity is email. The "From" field is a collection of entities. If any of these entities is accessed, the attributes are from the entity Activity Party.

[IntelliSense]: Recursive resolution of Delegates

Even in more complex scenarios like "delegates", the entity name is resolved, and the correct attribute result list is shown. 

 

[IntelliSense]: Support for context specific Relationships 

The first entity will be associated. The "Relationships" are suggested depending on the first entity.

[IntelliSense]: OptionSet Values (Condition)

An Attribute with the type OptionSet is chosen, and its value is compared. Now depending on the used OptionSet field, possible OptionSet values are suggested.

[IntelliSense]: OptionSet Values (Assignment)

The OptionSet field from this entity is set to one of the suggested OptionSet values.

[IntelliSense]: Support for Entity Relationships

In a LinkEntity, the first two parameters are entities, and the following two are attributes. The first attribute parameter only shows attributes from the first entity parameter and the second attribute parameter only shows attributes from the second entity parameter. 

[IntelliSense]: Constructor Properties

An attribute will be retrieved. The EntityLogicalName is suggesting all entities, while the LogicalName is suggesting attributes depending on the used entity.

[Command]: Convert FetchXML to C# Query Expression

Saving your time from manually converting a FetchXML on-the-fly to a equivalent C# QueryExpression

Use Cases:
When a developer has an existing FetchXML to query data, and needs that in C# code, he/she has to convert it to a Query Expression