Primary Action not showing in view

The view in question is based on a slice, yes, the action is included in the slice.

It’s a table view within a dashboard (but the action does not show either on the dashboard view or when I open the table view itself).

After the action did not show initially, I copied another action which DOES show and just changed it’s mechanics, still no luck. It DOES show up when I change it to inline, but not as primary OR prominent.

It’s only those 2 actions, so not related to any limits for number of actions showing or such - I seem to remember there are limits, but I have other views showing multiple actions as primary.

No “only show if” restrictions.

Any ideas what else to double check and/or what might be the issue?

Please post some screenshots of the involved action, view, and slice configurations.

2 Likes

The fact that you said it shows as an “Inline” action implies that it is probably a row-level action? Row level actions WILL NOT shown on Table Views or Dashboards - because they need a specific row in context in order to operate.

Could that be the issue? If not, providing details as described by @Steve would be very helpful to nail it down.

2 Likes

I believe you need to enable this option.

2 Likes

What the action is supposed to do (and successfully does, if displayed as inline action and clicked): Set a specific cell in table “Triggers” to the current timestamp to trigger a Google Script. Nothing fancy. I’d like to have this as a button on the top level “new eMails” view.

This is the action that’s not showing:

This is the view:

And this is the slice (note the action “Fetch Mails” is included in the slice actions:

It is already enabled, that’s not it. But thank you!

1 Like

Could @WillowMobileSys be onto something re: this being a row level action? The way it’s set up, this action does not NEED any row level data, but if the action type itself is the issue - how would I use a non-row-level-action to simply set a timestamp in another table? The only action types specifically saying “not a row level action” are useless here (import/export CSV, open form)

1 Like

This activity would be a row-level action. You can’t set a timestamp on a table, but are setting the timestamp on the rows of a table - even if it might be ALL rows.

Can you describe your situation? Why do you need to set a timestamp across an entire table? Why couldn’t the timestamp be set on each row as it was added/edited?

1 Like