Hi community,
In the past we used SLNet calls to create an enhanced service elements in a QAction. While doing so, there is the option to assign a visio (using the VdxFileName property) to the element during the element creation as shown below.
AddServiceMessage addService = new AddServiceMessage();
addService.DataMinerID = iDmaId;
addService.HostingDataMinerID = iDmaId;
addService.ViewIDs = new Int32[] { iView };
ServiceInfoEventMessage service = new ServiceInfoEventMessage()
{
DataMinerID = iDmaId,
ElementID = -1,
Name = SecurityElement.Escape(sServiceName),
ServiceElementProtocolName = "ProtocolName",
ServiceElementProtocolVersion = "Production",
ServiceParams = sFilteredElements,
VdxFileName = "Visio.vsdx",
Properties = sServiceProperties.ToArray(),
};
addService.Service = service;
object result = protocol.SLNet.SendSingleResponseMessage(addService);
Now, we want to use idms calls instead of SLNet calls because of syncing issues and obviously SLNet calls are not the recommended ways. I can create elements/services with the idms calls but I couldn’t find a way to assign a visio to the service during service creation.
Note that the protocol of the element is an Enhanced Service Protocol. As per the answer to this question, it is not possible to assign a visio to an Enhanced Service Protocol so that it will automatically assign the visio to the element.
So, is there a way to assign/associate a visio to a service when the service is created using idms call?
Hi Fenta,
As far as I am aware IDMS calls do not have support for manipulating the assigned Visio files at the present time.
You will have to continue resorting to SLNet calls for the time being.
Feel free to leave a Feature Suggestions - DataMiner Dojo regarding improving IDMS and extending the support.
Thank you Joao. I added the following feature suggestion: https://community.dataminer.services/new-feature-suggestions/improve-idms-call-to-support-adding-visio-when-creating-an-element-service/