Can you describe this page and process in a little more detail? When you're creating a new record on object A and saving it, are you then expecting the lookup relationship to show up on object B's record? Depending on how your page is set up, you may just need to re-query the relevant model.

I have a Wizard component where in the second step ill populate the fields related to master object. Once i hit the next step button i will taken to the detail object layout (Within the wizard) by creating master record. Here i will fill in the detail objects fields and will save it. This way i'm saving both master and detail object records. But when go to its detail view, i don't see the lookup field populating.

The actions i have on the next step button (layout where master object fields are showed) is

I added re query action on the save button within the wizard component. But no luck.

i want to mention some thing here.

If you look at the below screenshot, There are two Look-up Fields. One is Requested By and the other is Manager name. Requested By is populated whenever with the logged in users name. and Manager name field is manually entered by looking up in to the user object.

Now, when i open the Detail page, i am getting the following view.

here the requested by is populated properly but the Manager Name field id not populating. But if i look at the record in its classic view i see the name on the Manager Name Field.

What does the Manager Name field look like on the model itself? It sounds like this field is being pulled into the Skuid page in a way that's making it read-only.

For example, if I want to create a new Contact record, and associate it with an Account record, I would use the AccountId field on the Contact object for this. If I were to try and save the Contact record with changes to Account.ParentId or Account.Id, it wouldn't work because this method of bringing in fields from a related object provides read-only access.

Another possibility: If both of the fields you highlighted in the above screenshot are set up in the same way, and one field is being saved while the other is not, you may need to look at the way the fields themselves are set up in Salesforce, and compare the permissions and security settings to see if the Manager Name field has any settings protecting it from receiving changes.

i exactly don't know what the issue is but just now i created a new lookup field with the similar behavior and it is working absolutely the way i wanted. This is totally weird. This to me sounds like, two custom fields with same behavior. but one among them is not working.

Anyways my issue was resolved. Thank you very much working with me on this issue.

If you're attempting to create a lookup to the Standard User Object, unfortunately it sounds like Salesforce does not allow that kind of relationship on the User Object. More information can be found here.

I'm pleased that you were able to find a solution - would you mind describing what you did differently?

Sure.
I was trying out different things and as part of it, i created a new custom lookup field looking up to user object. that's it. It worked. I see the value i entered during the record creation showing up in the detail page

This is not the first time i'm linking a custom field to Standard user objects data. Every time i created such a lookup relation, it worked. But I still couldn't figure out why that particular field failed to populate the field value. I checked the field permissions and everything looked same.