Hi Kelvin,

Can I assume that adding Electronic Document Types (EDTs) is a system setup thing that does not happen that often? Or is there some more automation required for adding it in your API toolbox?

May I point you to ISHRemote's Add-IShEdt cmdlet. So on https://github.com/RWS/ISHRemote/blob/master/Source/ISHRemote/Trisoft.ISHRemote/Cmdlets/EDT/AddIshEDT.cs you'll find the help illustrating those field names you are looking for (line 35-37) and lower in the file the API call that uses them (line 136).

And as EDT is just another card type with fields, you can use ISHRemote's Get-IShTypeFieldDefinition to find out:

• What are mandatory fields (column MM, where first M points to Mandatory or not; and second M to multi-value or not)
• What are fields required on Create (column CRUST, where C means Create)

> Get-IshTypeFieldDefinition | Out-GridView

This should get you going,

Best wishes,
Dave

Hi Kelvin,

Can I assume that adding Electronic Document Types (EDTs) is a system setup thing that does not happen that often? Or is there some more automation required for adding it in your API toolbox?

May I point you to ISHRemote's Add-IShEdt cmdlet. So on https://github.com/RWS/ISHRemote/blob/master/Source/ISHRemote/Trisoft.ISHRemote/Cmdlets/EDT/AddIshEDT.cs you'll find the help illustrating those field names you are looking for (line 35-37) and lower in the file the API call that uses them (line 136).

And as EDT is just another card type with fields, you can use ISHRemote's Get-IShTypeFieldDefinition to find out:

• What are mandatory fields (column MM, where first M points to Mandatory or not; and second M to multi-value or not)
• What are fields required on Create (column CRUST, where C means Create)

> Get-IshTypeFieldDefinition | Out-GridView

This should get you going,

Best wishes,
Dave

Hi Dave

Thank you for the useful information! I got it to work.

I agree its not a common occurrence to add EDTs. Just doing some experimentation in case we need to support many new extensions in future.