I have a question for those who have spent a lot of time working with Slices, Linktofilteredview expressions, and working in table views with ‘inline’ behavior-actions.
What I’ve noticed is that Slices on more complex apps can become a bit difficult to maintain, so I looked for an alternative, and the one I settled on was the Linktofilteredview expressions inside of actions that sit alongside the table rows… like so…
A formula would then be placed in the action button (set to App: Go to another view in the App), like so…
IF([Code2] = "F", SWITCH([View], "Employee Register", LINKTOFILTEREDVIEW("Employee Register", [Area] = "A"), "Incident Register", LINKTOFILTEREDVIEW("Incident Register", [Area] = "A"), "Training Register", LINKTOFILTEREDVIEW("Training Register", [Area] = "A"), "Timesheet Register", LINKTOFILTEREDVIEW("Timesheet Register", [Area] = "A"),""), LINKTOVIEW([View]))
Using these formulas, along with a few other expressions means I can now bypass having to use numerous slices and views for the same result.
My question is, for those who have had experience with both these approaches, am I going to run into any unforeseen issues? I’m worried about action buttons in general as I’ve had some negative experiences in the past. So far the only the downside I’ve encountered is that when placing two different actions on the same in-line column, they are placed at an offset instead of on the same vertical alignment. This means if you want to use a number of these actions within the same table view, it can get a bit messy from a visual standpoint. I can live with this though, because it brings so much simplicity to organizing my app and any future cosmetic / structural updates so the positives seem to greatly outweigh these issues.
Thanks for reading guys, any feedback would be much appreciated.
