Skip to main content
M
marcot345826
April 14, 2025
Question

Can't find table when writing to a record

  • April 14, 2025
  • 4 replies
  • 0 views

I can't tell if this is an appian problem or a DB problem and am not sure where to begin looking for the problem. When writing to a record I get this error:

I wasn't getting this error last week, which is frustrating, but I am now. As far as I can tell, I haven't changed anything that I am aware of that might cause it. The table exists in the db and the table permissions seem to be fine. Doesn't seem to be happening with other tables and I don't have access to appian's error logs. Any ideas as to what I should do next? 

4 replies

Z
zakarym8213
April 14, 2025

First thoughts on this are with casing and object permissions.  I recommend you check the casing of the table defined on the record and confirm it matches the actual table name in the database? You mentioned that the table permissions seem to be fine, but check that the same is true for the object security.

M
marcot345826Author
April 14, 2025

I can't imagine casing is an issue as I've written with this record before and am still able to use the record to read the data. I checked to be sure, and it seems fine.

 

I've got direct admin permission to both the record itself and the process model I'm writing with and haven't configured any other security on the record. 

M
marcot345826Author
April 14, 2025

I swear the appian gods are purposely trying my patience today. So I've been trying to rebuild the table/record that is malfunctioning and for some reason when I generate record actions for it, appian generates the record actions in a completely different application. I've tried deleting them and redoing the record 3 times thinking I must have clicked something wrong along the way, but no, every time the files get generated in a different application instead of the one I'm working in...

M
marcot345826Author
April 15, 2025

Well, it's definitely an Appian problem, not a DB one because I created a new record to write to that table and it wrote fine. I could switch to the new record in theory. But the problem is switching everything over to the new record will take days of rework and I've no guarantee this issue won't come up again. Any ideas what I should be looking for in the record to fix this? 

Terms & ConditionsAccessibility statement