Thank you everyone. I know that here I am trying to let "Import" do something it is not designed to do. The business case here is that I have data store in SQL editor component. Ideally, data here will be pushed from SQL Editor to the Origin "Import" because I would like to leave Origin "Form" as another way for user to input manually. An alternative is to use another dimension such as UD, but I would not want to create a new member if not 100% necessary.
Kai
Standard Workflows (Import > Validate > Load) can source data from any SQL table. Consider making it a Direct Load so that it skips all of the audit log and it should be pretty fast. It might be even easier to maintain than a BR depending on the complexity of the data.
Edit: SQL table with Import > Validate > Load is essentially what a good number of the register based marketplace solutions do (People Planning, Capital Planning, etc.)
Thank you! I know the example in People Planning. However, in my example, it could cause problem because import - validate - load always needs to be implemented at the very last step, because the processing bar will push all the way to the end, and completes the workflow. In my use case, user needs to save the data in the register, and then the data is supposed to go to the cube immediately. Then user need to go back and work on the register for another account, and save the data again. In other words, the work cannot be done in one saving, or it would be too much data entry in the register for one time. If I implemented the same as people planning, the workflow will be completed every time user saves data. In order to continue working on the register, user has to revert workflow to continue using register, which is very time consuming.
Thus, I am thinking of the way to push data direct to import without bothering the "import - validate- load". Hope this explains. Thank you very much db_pdx for your input.
Kai
I see now. With that iteractive cycle it makes sense why you might want to load just select cells in a rapid fashion. Sounds like Cristian's suggestion might be the way to go. Also, this sounds like a fun use case in OS!
I'll stop pushing the Import > Validate > Load after this last thought. You could always choose to separate the Import > Validate > Load from the SQL Table Editor. The table editor would live in Workflow profile or just 'Workspace' (as a dashboard) and then Import > Validate > Load would be a sibling workflow to this workspace. Your button would trigger the Import > Validate > Load harvest without needing to finalize your Workspace profile.
Good luck with the project! Cheers,
-db
