Requests not linked to incidents or cases when Create Request UI action is usedIssue When the Create Request UI action is used from a parent record such as an incident or case, the resulting catalog request is not linked back to the originating parent record. This occurs when the glide.sc.use_cart_layouts system property is set to false. The linking between the catalog request and the parent record requires this property to be set to true. Example: Create a brand new Catalog Item.Configured the form to show the 'Use Cart Layout' field on the form.Unticked or set the field to false.Open an existing Incident/Case record, from the context menu, click on 'Create Request', select the newly created Catalog Item, complete the fields and submit.The new request was not linked to the incident/case record. Release Any Cause When glide.sc.use_cart_layouts is set to false, the cart layout feature is disabled. The Create Request UI action relies on the sc_layout-driven cart macros to carry the parent record association through the transaction. When these macros are disabled, the association between the catalog request and the parent record is not preserved. Resolution To restore the link between catalog requests and parent records, set the glide.sc.use_cart_layouts property to true. 1. Log in to the instance with the admin role. 2. In the Filter Navigator, type `sys_properties.list` and press Enter. 3. Search for the property named glide.sc.use_cart_layouts. 4. If the property exists, open the record and set the Value field to true, then save. 5. If the property does not exist, create a new system property record with the name `glide.sc.use_cart_layouts` and the value true, then save. Related Links - Create a request from another flow