Hello,
When I import either a csv or excel file. the records do not appear on the data store.
I do not have access to view the database but the files make it to the target folder.
Thank you for the help
Discussion posts and replies are publicly visible
Is there an error in the process? Did you check the logs for more details?
Hello Mathieu,
When I use the Import Excel To Database smart service, I do not get an error and I am unable to access the system logs.
When I to use the readexcelsheetpaging() function, I am able to view the data in the Expression Test Output (RAW).
When I to try write the data to a CDT, I get a CastInvalid error. I am really not sure what else to try here.
Expression
a!writeToDataStoreEntity( dataStoreEntity: 'recordType!{5d8ec9f2-52c8-4946-a0e8-9ae5ed74aac5}AIC Demographic', valueToStore: fn!readexcelsheetpaging( excelDocument: ri!importdata, sheetNumber: 0, pagingInfo: a!pagingInfo( startIndex: 1, batchSize: 1000, ) ),)
Test Output Error
Expression evaluation error at function a!writeToDataStoreEntity: Could not cast from RecordType to Data Store Entity. Details: CastInvalidCould not cast from RecordType to Data Store Entity. Details: CastInvalid
This is the issue I am running into. When using the Import Excel to Database node, the data never appears in the database. However, the file is created in the target folder.
The WtDSE node is attended to write the imported excel file (pv!HelzleImport) into DSE AIC_demographic
Is there a certain node to transform the data?
The problem is that you use a synced record, but the import plugin does not trigger that sync. So Appian does not "know" about the new data. For a simple test, just trigger a manual sync in the record.
I have tried to manually sync and there is still not available. I have seen in other threads that using the readexcelsheetpaging() function is the best method for more flexibility and consistency.
You mention earlier to
The problem with readexcelsheetpaging is, that it does not scale with larger volumes of data.
To find out what is going on, you need access to the database. And when there is not data imported, then the Excel file is empty, the configuration of the node is wrong, or an error happened during import. Now, that's for you to find out.
OK. Thank you for all the help. What exactly would I need to find out with access to the database. I can tell the Console Admins to look for me.
The excel file has data
The node is configured correctly. I have
Data Source Name: ="jdbc/Appian"Excel Document: =pv!HelzleImportTable Name: ="aicdemographic"
It's funny to see my name in a variable.
You need to check for any error messages. The node has some outputs you can configure to check for any errors.
I want to make sure to create a new process.
I am not getting an error when running the node. Is there any other recommended way to read a excel file and store it locally?
That node will complete but could still return an error message. You have to check the content of the process variables.
where exactly would I find the content to check
here is a screenshot from Generate Documentation
When monitoring the process instance, you can check the content of process variables.
https://docs.appian.com/suite/help/23.2/Monitoring_and_Editing_Processes.html
I wanted to thank you for all your help. I taken a refresher in the Academy to better familiarize myself with data store entities and records types.
After alot of review, I noticed Appian changed the names of the database and the column headers. I am now attempting to solve why my updates to the XSD file does not reflect on the Data Store when saving and publishing. When I create a new version of the XSD, the Data Store doesn't verify the changes. When I check the DDL script, the changes are there.
I dont have access to the database console, so I have just been recreating new base data types to resolve my issues. But I know this is not best practice. And will not lead me to reading excel files with multiple sheets and storing them into their specific CDT within the data store.
But again Thank you for your guidance. My journey continues onto managing historical data and case management with Appian.
That's great to hear. I know that it takes a while to wrap your head around the concepts of Appian in the beginning. And especially without a guiding senior at your side. Have fun and keep rocking!