Hi guys,
I was using this "Export DSE to Excel" SS in replacement for "Export CDT to Excel" SS which is deprecated in recent version. So the problem is , they have declared CDT in the start node variable and did some changes in the script task afterwards and pass the PV as CDT in older version. But the new version is throwing error while giving the PV as CDT. Is there any way to solve this. I need help ASAP.
The error message and the process model structure.
Thanks in Advance.
Regards,
Kavya
Discussion posts and replies are publicly visible
export CDT to excel & export DSE to excel works different ways. In export DSE to excel you need to define DS Entity, selection , filter etc like a query entity it will work. you cant pass cdt inside export dse to excel
Is there any other component to replace the deprecated one other than export DSE to excel? Could you suggest anything?
These smart services are not provided by appian they are from Plugins. You can search for the smart service you are looking for in Appian Appmarket. I am not aware about any other PLUGIn which can replicate CDT to excel
Thanks for the suggestion.
The deprecated plug-in nodes still work, and there has been no sufficient replacement provided yet.
IMHO, anyone who depends on these for their use case should continue using them unless they have an important reason to discontinue.
Thanks for the response. I somewhat included the script component function in the filter of the SS. Now I want to include some constant values like headings (like name of the report) to my excel to make it somewhat presentable. Any suggestions for that?
Without knowing your exact specifics, I assume you can use some combination of editing the base Excel template, and also using the individual cell functionality in the smart service (the "cell_keys" / "cell_values" inputs which can be used to set individual cells to arbitrary values).
I have tried giving a template in the update document instead of creating new one to add those additional things. For first process it works good and got my required report. But the output is stored as template doc, So the next process the template already got the values in it. I can't use any template I think so. Any idea?
Are you still referring to the Export Data Store Entity to Excel node, or Export CDT to Excel?
With Export DSE to Excel, I believe you can create a pv!exportDocument variable which is defaulted as a copy of your template document. In the Document to Update, use this pv! instead of the reference to the actual document, and you will update the local pv! document vs updating the base template.
In Export CDT to Excel, you can reference the document directly in the Excel_base_template parameter, and save the exported doc via the node outputs "Output_document" parameter.
I also rely on the deprecated Export CDT to Excel service regularly as there is no suitable replacement at this time.
Chris said:I believe you can create a pv!exportDocument variable which is defaulted as a copy of your template document.
Correction: it (export DSE to Excel) overwrites anything you attempt to provide as a 'template', even with the new changes in 21.4. The only way around this is to use the Copy Document (plug-in) Smart Service and make a dummy copy first. It's ... flabbergasting.
Guys, We don't get what we want in Export DSE to Excel. So we went for Export SQL to Excel. Thanks for all those suggestions.