# Show detail screen

**URL:** https://community.glideapps.com/t/show-detail-screen/79173
**Category:** Ask for Help
**Created:** [January 13, 2025, 7:10pm UTC](https://community.glideapps.com/t/show-detail-screen/79173 "2025-01-13T19:10:26Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![Lomanto](https://avatars.discourse-cdn.com/v4/letter/l/7993a0/32.png) [@Lomanto](https://community.glideapps.com/u/Lomanto)
#### Post date: [January 13, 2025, 7:10pm UTC](https://community.glideapps.com/t/show-detail-screen/79173/1 "2025-01-13T19:10:26Z")

</div>

Good afternoon,  
I’m using SHOW DETAIL SCREEN to show some information.  
However, when returning to the previous screen, some things need to happen.  
I can put a BUTTON to do this and put an ACTION to execute what I need, but if the user clicks on the return arrow the APP gives an error.  
Is there a way to put action on the Back Arrow? If it’s not possible, could anyone tell me how to hide it?

---

<div class="post-metadata">

### Author: ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)
#### Post date: [January 13, 2025, 7:38pm UTC](https://community.glideapps.com/t/show-detail-screen/79173/2 "2025-01-13T19:38:43Z")

</div>

> [@Lomanto](#):
>
> APP gives an error.

What kind of error do you get?

Would it be better to perform those actions on the way into that detail screen instead of on the way out?

---

<div class="post-metadata">

### Author: ![Lomanto](https://avatars.discourse-cdn.com/v4/letter/l/7993a0/32.png) [@Lomanto](https://community.glideapps.com/u/Lomanto)
#### Post date: [January 13, 2025, 7:42pm UTC](https://community.glideapps.com/t/show-detail-screen/79173/3 "2025-01-13T19:42:01Z")

</div>

Sorry  
I didn’t express myself well.  
it is not a mistake.  
I need to execute a set column and using the back arrow the fields are not cleaned and the application does not meet the need.

---

<div class="post-metadata">

### Author: ![Lomanto](https://avatars.discourse-cdn.com/v4/letter/l/7993a0/32.png) [@Lomanto](https://community.glideapps.com/u/Lomanto)
#### Post date: [January 13, 2025, 7:44pm UTC](https://community.glideapps.com/t/show-detail-screen/79173/4 "2025-01-13T19:44:42Z")

</div>

![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/d/e/dee24a35a5fff14349e3a08ff80973323b8c95aa.jpeg)

---

<div class="post-metadata">

### Author: ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)
#### Post date: [January 13, 2025, 7:46pm UTC](https://community.glideapps.com/t/show-detail-screen/79173/5 "2025-01-13T19:46:33Z")

</div>

You can’t place an action on the back arrow. You can hide it with CSS, and create your own button with a set column and go back action, but that won’t stop anybody from using a browser back button or the back button on Android for example. A user could also just close the app to get out of the screen.

That’s why I suggested doing your actions on the way into the screen instead of the way out. You have a lot more control over how a user gets into a screen, but not how they get out of it.

---

<div class="post-metadata">

### Author: ![Lomanto](https://avatars.discourse-cdn.com/v4/letter/l/7993a0/32.png) [@Lomanto](https://community.glideapps.com/u/Lomanto)
#### Post date: [January 13, 2025, 7:49pm UTC](https://community.glideapps.com/t/show-detail-screen/79173/6 "2025-01-13T19:49:15Z")

</div>

You’re right, if the user returns via cell phone it will continue to go wrong.  
Thanks

---

<div class="post-metadata">

### Author: ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)
#### Post date: [January 20, 2025, 7:49pm UTC](https://community.glideapps.com/t/show-detail-screen/79173/7 "2025-01-20T19:49:45Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
