Detail View "Clears" after new row is added

Hi, I have a Deck with a Grouped Action tied to the Row Selected event. The Grouped Action does two things:

  1. Add a new record to a different table (an activity logging table). Using this: Data: add a new row to another table using values from this row.
  2. Show a detail view using this: App: go to another view within this app

The Grouped Action works when I select a row in the deck. The record IS logged in the table and the detail view is rendered properly. The PROBLEM is that after a few seconds the Detail View just “clears” and the view is a blank screen (the data is cleared out). Does anybody have any thoughts on this?

Screenshots:

The Deck:
deck1

The Detail view BEFORE it "clears"
detail_view

The Detail view AFTER it "clears"
blank_view

The Actions


Screenshot 2021-02-13 at 5.34.43 PM

Sounds like the slice might be clearing itself - that’s why it goes blank?

Thanks for reply @MultiTech_Visions . It does seem to be something like that. I just don’t know why it would be clearing the slice. I’m not updating any data in the slice that supports the detail view.

It issue seems pretty clearly tied to the FIRST action (updating a row in a different table). When I remove that action the detail view renders just fine and does not ‘clear’. Maybe somehow the flow here works out like this:

  1. Queue the record to insert to a different table (not actually inserted yet)
  2. Render the detail view (renders okay at this point)
  3. Record queued for insert is actually inserted
  4. Detail view “clears”

I’m wondering if somehow the Detail view is “receiving” a response from the Record Insert (in a completely different table) and that response doesn’t correlate with anything the Detail view recognizes (and thus “clears” out the detail view).

I’ve seen this behavior when a newly-added row the view is displaying becomes unavailable as the data is synced in the background. For instance, if the row was added to a table with a security filter that happens to filter-out that row; or a workflow (which is performed when the data syncs) deletes the row.

1 Like

For what it’s worth I figured out what was happening here. The action Data: add a new row to another table using values from this row caused some Random Number formulas I had set up in the source spreadsheet to recalculate. Those same random numbers what is used to SORT the underlying DECK view I have (I may need to re-visit sorting off of a Random Number formula…the idea though is to give the user some variability in the results they see). When the Random Numbers recalculated it resorted the deck which ‘moved’ the “current row” apparently which caused the detail view to kind of lose it’s place so-to-speak.

I change the Data: add a new row to another table using values from this row to update a completely separate spreadsheet (so the Random Number recalc’s aren’t triggered in the main source spreadsheet) and the issue was resolved.

1 Like