Hi Ronald.  vRO uses specific ViPR API calls to perform specific actions.  If the API is not wrapped into a vRO workflow operation, then there is no way in current solution to call it.  The API error response is telling you to use the 'update' API, and not the 'create' API which is what the create workflow is using.  Sounds like you need an enhancement request (send me an email with customer name and your detailed requirements use case - sounds like pretty straight forward) which I can raise for you.  Alternative is to engage in coding of vRO plugin and customizing workflow - that will require some PS hours, but there are specialists out there that can do it. It will also not be supported by standard support procedures since it will be custom code owned by the client.  Stanislav
Anyone using VMware vRO and it's ViPR controller plugin to create/modify NFS?  Need to be able to alter existing rules to add IPs for access.  Basically if I rerun the export workflow, I get the following:  [2017-04-01 10:42:29.195] Error in (Dynamic Script Module name : init#383) Error: Filesystem export failed with error: Error 1013: File System has existing export. To modify the export and its rules, please use update URL.  [2017-04-01 10:42:29.229] Workflow execution stack:  *** item: 'Export EMC ViPR File System/item1', state: 'failed', business state: 'null', exception: 'Error: Filesystem export failed with error: Error 1013: File System has existing export. To modify the export and its rules, please use update URL.  (Dynamic Script Module name : init#383)'  Thanks for any insight.
NFS Export Rules Update