drivardxrm / xtb.customapimanager Goto Github PK

Found a bug where the parameters and properties are not properly cleared when creating a new API after creating a first one

Looks like OnPrem v9.1 doesn't support WorkflowSdkStepEnabled and when opening the tool or trying to create new API, I get an error:

Error occured: 'customapi' entity doesn't contain attribute with Name = 'workflowsdkstepenabled' and NameMapping='Logical'.

I did check EntityDefinitions, and workflowsdkstepenabled is only available for sdkmessagefilter and sdkmessage.

Could you handle this case gracefully? Thanks.

I normally use the keyboard to tab through controls and most of the controls are not in order and had to use a mouse pointer to go to the next field on the form.

• Deployment: Online
• DB Version: 9.2.21093.152
• Connection Controls Version: 1.2021.9.46
• XrmToolBox Version: 1.2021.9.52
• Tool Version: 1.2021.7.54

When I try to create a response prop of type EntityCollection it gives me an error shown on the screenshot below. The issue is that I can't clear the Logical Entity Name field on the form to proceed.

Did you manage to create the EntityCollection output parameter or maybe it's still not supported?

• Deployment: Online
• DB Version: 9.2.21094.138
• Connection Controls Version: 1.2021.9.46
• XrmToolBox Version: 1.2021.9.52
• Tool Version: 1.2021.7.54

Thank you for #17

I found another difference between online/on-premises. The logicalentityname for customapirequestparameter and customapiresponseproperty is named... drumroll,,, entitylogicalname

PR is incoming.

There should be a way to add a given Custom API (+ Inputs and Outputs) to a given Unmanaged Solution.
Can be a bit tricky here.
All Custom API and components are created in the default solution at creation.

Since the components can be created at different moments (thus be already linked), need a way to add only the needed component when performing the operation.

Show info about the status of selected Custom API, Request parameter or Response Property

• IsManaged : Is the asset part of a Managed solution

• IsCustomizeable : Can the asset be modified if part of a managed solution

Should not allow to modify if Not customizeable
Should show warning if trying to modify a managed asset

the Bound Entity field is not showing on the Update Custom API form

When creating a new API, If you bind to an entity then select your plugin and save the bound entity will be aaduser regardless of your selection in the UI.

It works as expected if you select your plugin and then bind.

• Deployment: Online
• DB Version: 9.2.23104.216
• Connection Controls Version: 1.2023.6.56
• XrmToolBox Version: 1.2023.10.67
• Tool Version: 1.2023.10.218

Can you add a feature request that would allow for not selecting a logical name as it is not required for Request or Response Parameter?
This will enable us to use "expando" entity instead.

• Deployment: Online
• DB Version: 9.2.21101.144
• Connection Controls Version: 1.2021.9.46
• XrmToolBox Version: 1.2021.9.52
• Tool Version: 1.2021.10.57

Ca you please add StringArray and Guid in CustomAPIRequestParameter.cs and CustomAPIResponseProperty.cs

public enum Type_OptionSet
{
Boolean = 0,
DateTime = 1,
Decimal = 2,
Entity = 3,
EntityCollection = 4,
EntityReference = 5,
Float = 6,
Integer = 7,
Money = 8,
Picklist = 9,
String = 10,
StringArray = 11,
Guid = 12
}

There should be a section where we can see the Catalogs where a given Custom API is defined, there shouls also be a button next to each entry that open the 'Catalog Manager' tool with the given Catalog selected

Add support for this new field added to Custom API.
Field = Enabled For Workflow (workflowsdkstepenabled)

Add a 'Settings' section where some default values can be configured.

ex.
Enabled for workflow = True (on create)

hi,
your tool looks great!!
would it be possible to automatically create a swagger api documentation?