Hello!
I have a doubt that i can't quite solve yet, so posting it may let me solve it faster
I've followed an Appian advice in a way to download an Excel that has been exported from a Data Store Entity (something similar to this https://docs.appian.com/suite/help/22.1/Export_To_Excel_Smart_Service.html)
I've "been able" (finding performance problems, I guess due to the table size) to clean the data store entity before writing on it once again. However, I have 4 rich texts, one for each function (clean the DSE,
write to DSE, export DSE to Excel, download Excel).
I want to reduce the number of clicks needed to do so, so I thought on using a!startprocessmodel() to reduce the first 3 rich texts to just one (so I'd have 2 in total). The thing is, I'm struggling on the Write to DSE node due to not knowing how to configure it nor how to properly write the input variables to the process.
If you could help me do that or even reducing those 2 buttons to just 1 (I guess it would maybe be a download link of the process model output document?) it would be greatly appreciated.
Thank you,
Francisco
Discussion posts and replies are publicly visible
It seems like your issue is around "I'm struggling on the Write to DSE node due to not knowing how to configure it nor how to properly write the input variables to the process."
I suggest to do some testing with a more simple example to understand how to configure the node. Follow the documentation and tutorials to get an idea of how to do that.
The Write to DSE node takes a list of CDT items you have stored in the process or generate using an expression.
I think I now got how to do it, but since I basically did what you just wrote here I'll verify it as an answer
I created a list of CDT items (created using a dictionary to fit them in) but it looks kinda promising at the moment
My process model is delete from dse -> write to dse -> export dse to Excel. Is there anything that I have to do in order to get the generated document as an output variable? (if so, maybe I can refer to it in a a!downloadlink item to do it all in one click)
The export node will create a new document. Check the tab data->outputs. Store it to a process variable. Then enable chaining on all connectors up to the export node. Then you can reference this process variable in the parameter onSuccess of the a!startProcess() function.
Good morning.
It's looking good, however I have one last problem
I want to write more than one row at a time to the DSE, so in the "process parameters" parameter in the a!startProcess() function I tries creating a dictionary with createdictionary(keys: "DatatoWrite", values: {a list of dictionaries with the data I want to write}). However, I'm getting an error because it received 1 key and (length of list of dictionaries) values.
Any clues on how to fix this
Why not just make the PV a multiple? The write to DSE node can also handle a list.
BTW, createdictionary() is deprecated. Use a!map() instead.
I actually made it multiple in the process model configuration (made it required as well), that's why I thought making a dictionary with the value being the mentioned list would work. I think the mistake I'm making comes on the a!startProcessModel() function configuration (specially in the "process parameters" parameter.