I am, in all cases, using the logical names of columns. My schema names are the same, except that MS capitalizes them by default (e.g., logical name pub_column and schema name pub_Column).
I am including screenshots, but I'm not sure how much additional light they'll shed. To protect my client's intellectual property I have obfuscated the publisher prefix, the column names, and the table names except where they are relevant. In this example I'm referring to a lookup to the User table (systemusers), so there's no need to obfuscate the relevant names here (except the publisher prefix) since that's a system table.
Here is my first of two Get a Row by ID actions. The table "Table" contains a lookup to the User table, and it is referenced in the Select Columns:
In this image, I am referring to the lookup to the User table as "pub_user." as opposed to the format "_pub_user_value" that I've been using for years. As of the last few days, when I use the pub_user format, the column is available as dynamic content in the next Get a Row by ID action, as shown here:
However, as of the last few days, when I use the _pub_user_value format that I have always used, the column is not available in dynamic content for the second Get a Row by ID action (as it always would have been before):
When I go with the pub_user format that suddenly is the only way to allow me to select the column in dynamic content, I get this error on running the flow:
NOTE: In this case, the failed step is actually a "Get a Record By ID" step, but this happens on List Records steps as well.
When I use the normal _pub_user_value format in the Select Columns of the List Rows action, the flow doesn't error but I can't select my column in dynamic content while I'm building the flow. This is very different behavior than I've experienced with every flow I've built in all the years I've been doing this. I have always had to use _pub_user_value in the Select Columns (or in the Filter Query of a List Rows), and the columns referenced in that way have always been available as dynamic content.
I know I could use FetchXML to pull back the relevant columns from both [Table] and User at once, but I'm doing that in other places and this issue still happens. It is by no means limited to this specific example of looking up a User record. And, again, it just started happening recently.
