Create Data Source Entity (DSE) in Appian community version

The Appian CE does not support this. community.appian.com/.../community-edition-guide

Thanks for your answer. This did help

My goal is to attempt a POC to write into an excel template. Assuming the JSON data to populate the template would come from a rest service. What route is feasible to accomplish this in the Appian Community Version.

With the full version -  I am thinking with my current knowledge with Appian - "Export Data Store Entity to Excel Smart Service" is one option and using excel tool plugin would be another. 

Do you want to direct to any preference?

Thanks for your answer. This did help

My goal is to attempt a POC to write into an excel template. Assuming the JSON data to populate the template would come from a rest service. What route is feasible to accomplish this in the Appian Community Version.

With the full version -  I am thinking with my current knowledge with Appian - "Export Data Store Entity to Excel Smart Service" is one option and using excel tool plugin would be another. 

Do you want to direct to any preference?

Maybe a stupid question, but did you consider to query the data directly from Excel?

 padmanabant852500  you can use prebuilt template in webapi to export the data in CSV format without using any datastore entity 

AFAIK, APIs are also disabled in Appian CE.

Thanks for your answer. My goal is to write data into an excel template. Not to read. Idea would be to call a rest service which returns a json data, which will be used to write into the excel template

Thanks for your answer. My goal is to write data into an excel template. Not to read. Idea would be to call a rest service which returns a json data, which will be used to write into the excel template

You're on the right track! Since the data comes from a REST service, the first step would be to use an Integration to fetch the JSON data. Then, you can either directly map this JSON data to a record structure or use a process model to transform it as needed.

Once you have the data in a record (with a structure that matches your JSON data), you can create a read-only grid to display the data in an Appian interface. The grid will automatically have an "Export to Excel" button, allowing users to download the data in an Excel file format.

Since you're working in the Community Version, this approach will work well as long as you don’t need the "Export Data Store Entity to Excel Smart Service," which is available in the full version. If that’s the case, the grid export method is a good, simple alternative to generate your POC.

Thanks - I do have a sandbox now.

Attempting to work on a solution where I have a JSON with more than 250 values in a structured format. Need to write atleast 150 of them into an excel template in different sheets.

Its not a plain export.

We are also exploring the RPA to see how it can help.

But welcome any inputs.

My goal is to write into excel in multiple sheets using the "Export Data Store Entity to Excel" ability.

I may write few values from process variables too into the excel sheet - apart from what I have in the database.

So I have an excel sheet as template and wanted to leverage the "Custom Cell Positions" and "Custom Cell Values" ability in the "Export Data Store Entity to Excel" smart service to put in the values in the desired position of the excel sheet.

But I keep getting this error.
"Custom cell positions cant refer to cells below the starting cell. Otherwise, they would be overwritten by data being exported. (APNX-1-4505-037)"

I tried to use this simpler option too and still get the same error.
Custom Cell Positions={"A6", "B6", "A7", "B7"}
Custom Cell Values={"Value for A6", "Value for B6", "Value for A7", "Value for B7"}

My excel template does not have any values beyond the 2nd row.

Does the "Custom Cell Positions" and "Custom Cell Values" ability really works when we attempt to write into an excel template (excel template name is mentioned in Document to Update").
This does not work even when I use the "New Document Name" option.

Any input is appreciated