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
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.
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.’
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
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.
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).
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
