Create Document Automation Select

[lochtefeldm]

I have two sister applications and have created the same automation to generate PDFs, with a source table as the one difference.

Both automations are running successfully but the one table is not generating any data from the select function. I thought the issue may be due to security filters but removing it did not resolve the issue. The process is finishing successfully.

When I try to add another step to the process sending an email I do get this error: "Error encountered in step with name [New step 2]: The row used to populate the embedded app view (dynamic email) was either inaccessible or not found."

Any ideas what else could be the issue?

[Markus_Malessa]

---

@lochtefeldm wrote:

same automation to generate PDFs, with a source table as the one difference.

---

Are you saying you are using two different 'database' tables? Might have something to do with different key column values or table names even. Hard to say without additional detail.

[lochtefeldm]

They both work from a mutual table, Nursing home profile table.
They have separate user tables where users keep a list of key values from the nursing home profile that they want to share. The document automation is suppose to pull values from the nursing home table for the related keys noted in the user table. 

Which is working in one app but not not the other for reasons I can't seem to identify. 

[Markus_Malessa]

There have been occasions where omitting [_THISROW].[COLUMN] in a filter condition did not yield any results. It is somewhat strange behavior because I have gotten select() to function both ways and I am uncertain why it did or did not work.

Still not quiet sure since we don't know what sets the bot into motion and what the inputs are.

[lochtefeldm]

The bots are set in motion by a row being added with a column containing a value. They are both producing a pdf. I just can't seem to understand why one is producing an actual list and the other is producing a pdf without row data.

For the data its suppose to select, its comparing the key column in the nursing home data table to an identical column in the user table. So there isn't one row its working from, its looking at all rows in the nursing home data table where there is a match in the column  [CMS Certification  Number] in the user table. 

[Markus_Malessa]

I think I replied privately to your last response which might have also been private. In your select() formula [_THISROW] might apply if you are using a column that is named the same in two different tables, which appears to be the case in your setup. Check the private reply and see if it makes any difference.

[lochtefeldm]

Correct, the column has the same title in each table. I have it structured that way in both applications. I don't see a private reply.

Are you saying to adjust it to-

<<Start: SELECT(Nursing Home Data[_THISROW], IN([CMS Certification Number], SELECT(User Files[CMS Certification Number], TRUE)))>>

[Markus_Malessa]

This way actually:

<<Start: SELECT(Nursing Home Data[CMS Certification Number], IN([_THISROW].[CMS Certification Number], SELECT(User Files[CMS Certification Number], TRUE)))>>