@rpersad
The problem seems to be related to how Power Apps handles navigation and variable persistence. It could be that when you navigate away from the page where the variable gblCurrentRecordNew is defined, the value might be lost or reset.
When using the Navigate function in Power Apps to move between screens, only certain types of context variables are passed to the new screen. Global variables, like gblCurrentRecordNew, should retain their values across different screens. However, there may be some nuances to how you're handling data that could cause the variable to lose its value.
Here are a few troubleshooting steps:
1. Ensure gblCurrentRecordNew is indeed a global variable and not a local one. Remember, global variables are defined using the Set function, and local variables are defined using the UpdateContext function.
2. Check the button that navigates to the detailed page. Make sure you're not unintentionally resetting gblCurrentRecordNew during this navigation.
3. On the detailed page, use a Label control to display the value of gblCurrentRecordNew.'Contact Number'
This will help to confirm whether the issue is with the form or the variable.
Remember, in the detailed form you should also use gblCurrentRecordNew.'Contact Number' instead of ThisItem.'Contact Number', as the context ThisItem is not available.
You may also want to consider an alternative design approach where you set just the item id and then use the LookUp function to fetch the item again from SharePoint based on this item id. This way, you ensure that the item is fresh and loaded when the detailed screen is shown.