Forum Discussion
Hi Kris,
You can only call a connector business rule from an import workflow step.
Now what you can do is automate the import validate load step from an extensibility rule to call your connector rule using an extensibility rule and you can then schedule it using the task scheduler.
You'll need API calls to build your extensibility rule.
wfClusterPk = BRAPi.Workflow.General.GetWorkflowUnitClusterPk(si, wfProfileName, scenarioName, timeName)
BRApi.Import.Process.ExecuteParseAndTransform(si, wfClusterPk, String.Empty, Nothing, TransformLoadMethodTypes.ReplaceAllTime, SourceDataOriginTypes.FromDirectConnection, True)
BRApi.Import.Process.ValidateTransformation(si, wfClusterPk, True)
BRApi.Import.Process.ValidateIntersections(si, wfClusterPk, True)
BRApi.Import.Process.LoadCube(si, wfClusterPk)
Thanks, Omkareshwar
Archetype Consulting
Thanks Omkareshwar. What API calls I require ? to call the connector rule ? Could you please explain more on this topic?
- Omkareshwar2 years agoContributor II
The connector can only be executed from the Import step so you're not calling the connector rule you'll be executing the Import Validate Load step from the Extensibility rule using those API calls. You can read this post to get more idea about that https://community.onestreamsoftware.com/t5/Workflow-and-Data-Integration/Automating-WF-Execution/m-p/10247
- Krishna2 years agoValued Contributor
Thanks this was Helpful.
- BSK11 months agoNew Contributor III
Hi kris,
Hope you're well.
If this automation is working at your end, could you please post the complete script snippet here, if that's possible. we do have a similat requirement to automate the data loads. Thanks in advance.
Related Content
- 4 months ago
- 3 years ago
- 3 years ago
- 8 months ago