This is probably because the object (in your homepage) is not coming directly from the database, which means that it is living in the browser's memory and whether you modify it in the same page or in a pop-up, the object instance in your homepage is the same instance in your pop-up. Depending on your design and requirements there are multiple ways to approach this (using a temporary non-persistable object that has the attributes that you’re trying to edit in your pop-up page and then copying its details to the object on the homepage on save or changing the source of your homepage’s data view to start getting the data directly from the database).
If that doesn’t answer your question, please edit your question to include a screenshot of your homepage and tell us more about your domain model (if you think it’s relevant) and your requirements.
If you only want the object to change (in the background) when a user saves their changes, you can do this by creating a non-persistent version of the object, which will be used for the editing part, and commit these changes to the persistent version object when a user saves them.
To do this you need to create a ‘copy’ of the object you want to edit in the domain model, but make this a non-persistent object. Create this object in a microflow when a user want to edit, and show the popup page. Edit this non-persistent object in the popup, and when a users clicks the save button, transfer these values to the persistent object in a microflow.
Hope this helps,