Skip to main content
pedroantonioa0001
pedroantonioa0001
January 13, 2021
Question

Error in Export Data Store Entity To Excel

  • January 13, 2021
  • 8 replies
  • 0 views

Hi.

I have one process configured to export data from a view to excel using the Export Data Store Entity to Excel, but somehow I'm getting this error: Error accessing data store entity: CIP_CrpStatus_VIEW. Please contact a system administrator for additional details. (APNX-1-4505-026), this view is trying to export 4814 records.

Has anyone experienced this error before?

8 replies

danny.verb
danny.verb
January 13, 2021

I would recommend checking security on the data stores. Make sure the user starting the process model and executing the smart service has at least Viewer access to the data store.

pedroantonioa0001
pedroantonioa0001Author
January 13, 2021

Hi, Danny The security in the data stored is fine also the node executes as whoever designed this process model, we did some test reducing the amount of information and it worked properly but it worked with around 600 rows that is to low, also this view is constructed by using two other views, do you know if this could be the issue?

danny.verb
danny.verb
January 13, 2021

Possibly, depending on the performance of the view. I recommend querying the view in the database UI to see what the performance is like. There's a chance the smart service could be timing out.

A
ananditab0001
March 9, 2021

Hi,

Is the issue resolved? If so, how did you achieve?

Thanks

pedroantonioa0001
pedroantonioa0001Author
June 10, 2021

Hi ananditab0001

The issue has been solved but we didn't change anything on the Appian process, apparently was an issue related to the database connection sessions we are using an Oracle database

P
poojas686639
January 22, 2026

I am also getting this issue frequently now , can u please suggest what have u done

S
sindhuv0001
June 10, 2021

Hi,

Has the issue been resolved? could you please share details on how you handled?

csteward
csteward
June 10, 2021

For the new posters here, note there can be different scenarios that generate similar errors.  I would suggest starting a new thread with the details specific to your use case, and we will be happy to take a look.  

Terms & ConditionsAccessibility statement