Getting Error as The 'Time Warp' component's 'Parent Record' property has an invalid value

[maheshbabusr]

Time Warp version
Setup->Apps->Packaging->Installed Packages. Time Wrap Version 1.15

Describe the bug
After Adding Time wrap component to parent asset flexi page and Whenever attempting to edit and save a parent asset Flexi Page, the system throws the following error:

"The 'Time Warp' component's 'Parent Record' property has an invalid value."

As a result, the Flexi Page cannot be saved until this reference is corrected. it's impacting on complete functionality of flexi page.

To reproduce
Steps to reproduce the behavior:

1. Go to 'Structure & Tunnels App' open Asset tab
2. Click on 'any parent asset'
   3.Edit the flexi page and save the page (it's throwing error here)
3. See error

Expected behaviour

Whenever attempting to edit and save a parent asset Flexi Page, system as allow to save the record without any Time wrap related errors

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Browser: chrome, Edge
• Time Wrap App Version 1.15

[github-actions]

Hello @maheshbabusr , thank you for submitting an issue we appreciate your time. We will take a look and give you an update as soon as we can. We aim for a 72 hour response time.

[spragerdev]

This is happening to us as well. It is directly related to our last Sandbox refreshes. A specific admin cannot save anything on a specific App Builder page layout. Not even a change in a text box.

[deejay-hub]

Hi @maheshbabusr. Replicating this will be key for us to know the cause. Hopefully you can provide some help.

• How many fields are on the parent object (Asset) in object manager?
• What value is populated in the Parent Record property? ('Use This Asset' or have you selected a field?)
• If you remove Time Warp from the Page can you save the layout successfully?
• Is the error only when you edit the page - or also when a user accesses the page?
• Approx. how many fields are in the standard detail section of the page layout?
• If you remove the component, then save, and re-add it back to the page layout what happens?

@spragerdev same applies to your scenario...can you take a look at the above and help us find some commonalities.

[maheshbabusr]

Hi @deejay-hub,

Thanks for your reply.. I agree that replicating the issue will be crucial to pinpointing the cause. Here's what I’ve found so far

In Asset Object as around 500 fields and in flexi page it's around 180 fields but with same fields and same flexi page is working in another sandbox like QA.
we are populating the 'Use This Asset' value in the Parent Record property.
yes, If remove the time Time Warp from the flexi page, system allowing to save page successfully.
Only whenever Edit the page and trying to save only error is Throwing.
Same Issue happening when we remove the component and trying to add and save again

Could you please check once and Do some needful to get the resolution.

Thanks in Advance..

[deejay-hub]

@maheshbabusr can you open the developer console and check the logs.

What we suspect.

1. You open the page. Parent record is successfully populated.
2. You save the page. Salesforce validates the selection
3. The Apex code that looks at the fields available causes a CPU time out so no matching selections are available
4. You get the parent record error

We would need you to use developer console to check for logs generated when you open the app builder page - and when you save the app builder page. We want to confirm that you see a CPU time out. We cannot replicate in our environment.

[maheshbabusr]

CPU Timeout Debug log.txt

Hi @deejay-hub,

Thanks for your quick response..

yes, we are getting CPU Timeout Error only, we have checked the log there we are populating only 'Use This Asset' value in the Parent Record property but in the logs it is showing Default_Picklist_Val as 2 more values not printing the values.

Please find the below screenshot and attached complete log file.

Could you please check once and Do some needful to get the resolution.

[deejay-hub]

We can't replicate the issue. The population of the parent picklist does use CPU intensive apex. Even with 500 fields on an object we cannot replicate the issue you see which is further complicated by the fact that you use different sandbox types. In theory if it fails on one sandbox it should fail everywhere - but that is not what you experience. We do know that a large number of fields, large number of fields on the page layout, multiple complex components on a page, large numbers of related lists etc - seem to make the issue more apparent.

What we have done to try and reduce the impact of our component:

1. Eliminated 4 Expensive String Conversions
2. Direct List Checks Instead of String Comparison
3. Early Continue Statements
4. Loop optimization to eliminate map lookups

This should reduce CPU time used by Time Warp considerably when editing properties in App Builder and the code is already in the cygni branch. We do not plan do package the code into a new managed release until Jan '26.

[maheshbabusr]

Hi @deejay-hub,

Thanks for your update..

Is there anyway to compile this code in to my instance...

[deejay-hub]

If you want to use the managed package from AppExchange you'll need to wait for a new version. If you want to use the code directly then all of it is in this repo for you to use, change and maintain as you see fit.