Add a slice/table name reference in the View documentation part

[Thagu]

When I have several slices (or tables) with many views, it would be beneficial to see, where my slice is used, to manage e.g. the impacts of changes to a slices to different views. For example I could answer the question if the deletion of a column in a slice has negative impact on certain views, if they use that column in the view or sorting option.

It could be implemented in the standard documentation feature of Appsheet:

 --> Settings, --> Information --> App Documentation --> "The documentation page for this app is available here"

[leefarrell]

It would be very helpful to see where slices are used across different views in AppSheet. This way, you can manage the impacts of changes more easily, like checking if deleting a column affects any views.

A great place to implement this would be in the App Documentation feature:

• Go to Settings
• Click Information
• Select App Documentation

This would make it easier to track slice usage and prevent unintended issues.

Thanks for considering this!

[hazelzoey1111]

To Add a slice or tabe name reference in the view documentation segment, include a clear and concise statement about the data source within the documentation section. Ensure the reference is easily identifiable by using bold or italic formatting. This enhances readability and provides quick access to the relevant data context for users reviewing the documentation.

[enginerd]

Does [ Settings -> Data -> Relationships -> Grid view ] provide everything you are looking for?

[Thagu]

@enginerd : "Does [ Settings -> Data -> Relationships -> Grid view ] provide everything you are looking for?"

--> no, there is only the grouping info on slice level listed. On the other side, I see no info on view level, neither.

Also in the graph view: the views are not listed explicitly with their names.

[Thagu]

@hazelzoey1111  "To Add a slice or tabe name reference in the view documentation segment, include a clear and concise statement about the data source within the documentation section. Ensure the reference is easily identifiable by using bold or italic formatting. This enhances readability and provides quick access to the relevant data context for users reviewing the documentation."

Actually a good workaround, but really prone to be outdated with the first change and time intensive to manage. And not well controllable... so no option for me with dozens of views and slices.

But thanks anyway for the input - for smaller setups it could work, I think.