# Image not saving to user-specific column

**URL:** <https://community.glideapps.com/t/image-not-saving-to-user-specific-column/68435>\
**Category:** Ask for Help\
**Created:** [December 6, 2023, 6:02pm UTC](https://community.glideapps.com/t/image-not-saving-to-user-specific-column/68435 "2023-12-06T18:02:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ckinross](https://avatars.discourse-cdn.com/v4/letter/c/3ab097/32.png) [@ckinross](https://community.glideapps.com/u/ckinross)\
**Post date:** [December 6, 2023, 6:02pm UTC](https://community.glideapps.com/t/image-not-saving-to-user-specific-column/68435/1 "2023-12-06T18:02:04Z")

</div>

Using the ‘generate image’ OpenAI functionality, a user uploads a photo which is then modified by OpenAi and a new image returned. Thank you to this community for helping me to reach this milestone.

Now, the odd part is the following

- (good) The image uploaded by the signed-in user gets loaded into the appropriate row
- (not good) The image generated by DALL-E gets loaded into the first row in the table rather than the row associated with the user
- Both of the columns (image upload and image generation) are user-specific

How do I have the generated image from DALL-E go into the appropriate user row?  
Thank you

 ![Screenshot 2023-12-06 at 9.55.59 AM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/1/e18742b0946b865402dc9a995dd8758108e1f5b2.png)

---

<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:** [December 6, 2023, 9:43pm UTC](https://community.glideapps.com/t/image-not-saving-to-user-specific-column/68435/2 "2023-12-06T21:43:14Z")

</div>

Usually when values are written only to the first row, that means that the screen you are working with is technically connected to that first row. You may need to explain in detail the process from the user uploading to their image up until the point when the AI returns an image. What is the flow. Which tables are involved. How are screens and actions configured. The columns being user specific shouldn’t really be a factor. I would think something is just misconfigured somewhere along the line.

---

<div class="post-metadata">

**Author:** ![ckinross](https://avatars.discourse-cdn.com/v4/letter/c/3ab097/32.png) [@ckinross](https://community.glideapps.com/u/ckinross)\
**Post date:** [December 7, 2023, 2:09am UTC](https://community.glideapps.com/t/image-not-saving-to-user-specific-column/68435/3 "2023-12-07T02:09:01Z")

</div>

Happy to share more details.

A user uploads a photo, which is submitted to OpenAI with a prompt.  
The original user image is added to their row as a signed-in user on the User table in a user-specific column called ‘Pet Photo Upload.’

 ![Screenshot 2023-12-06 at 5.23.01 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/8/0/804b88ee7cefd5a6ec7858c2c203f65d6c268c70.jpeg)  
The image returned from OpenAI gets shown on the same screen and logged in another user-specific column on the User table called ‘Image\_Santa’.  
 ![Screenshot 2023-12-06 at 5.25.05 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/7/4/749a9c6a63c0caa3dc407094c03bd8be33222257.png)  
 ![Screenshot 2023-12-06 at 5.27.19 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/b/9/b96fc08f0a0827a695fb60ca9084a8462a230650.png)

The desired outcome is that the image generated by OpenAI is logged in the same row as the original image in order to keep user-specific details together and avoid users seeing images that are not their own.

What other details would be helpful to share?  
Thanks

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [December 7, 2023, 2:18am UTC](https://community.glideapps.com/t/image-not-saving-to-user-specific-column/68435/4 "2023-12-07T02:18:58Z")

</div>

The fact that the image is being saved in the first row of the table suggests that either:

- you are not using Row Owners in your Users table, or
- the parent screen is not filtered (user is signed in user)

So my suggestion would be to check the above first. If neither of them are true, then the behaviour you see is expected.

> [@ckinross](#):
>
> user-specific details together and avoid users seeing images that are not their own.

That can never happen with user specific columns.  
That comment and the way you are using user specific columns suggests a fundamental misunderstanding of their purpose and how they work. Normally, there would be no reason to have user specific columns in a User Profiles table. User Specific columns allow users to have their own version of data in the _same_ row. Because each user has their “own” row in a User Profiles table, it makes no sense to use user specific columns. (There are some edge cases where it does make sense - for example to avoid syncing to external data sources - but this isn’t one of them).

---

<div class="post-metadata">

**Author:** ![ckinross](https://avatars.discourse-cdn.com/v4/letter/c/3ab097/32.png) [@ckinross](https://community.glideapps.com/u/ckinross)\
**Post date:** [December 7, 2023, 2:33am UTC](https://community.glideapps.com/t/image-not-saving-to-user-specific-column/68435/5 "2023-12-07T02:33:34Z")

</div>

You are correct, there are many things that I fundamentally do not understand (but I keep learning).  
Your insight regarding Row Owners solved the challenge.  
Thank you

---

<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:** [December 14, 2023, 2:33am UTC](https://community.glideapps.com/t/image-not-saving-to-user-specific-column/68435/6 "2023-12-14T02:33:40Z")

</div>

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