#Trailhead486 debatiendo

Hi Uttej, could you share a bit more detail about the CML configuration and the cardinality you’re trying to set for each level? 

In particular, it would help to know whether the GrandParent → Parent → Child relationships are configured as nested bundle products and what cardinality values you’re trying to apply at each level. If possible, please share the relevant CML snippet or a screenshot of the Browse Catalog configuration and the behavior you see after saving. 

That will help determine whether the cardinality can be applied to all three levels in this configuration. 

Hi Vikrant, autocomplete="off" isn't supported directly by lightning-input-field because it doesn't expose the underlying <input> element's autocomplete attribute. 

If you need to control autocomplete, you can use lightning-input instead of lightning-input-field and set: 

<lightning-input
    type="text"
    autocomplete="off"
    name="myField">
</lightning-input>

If you need to keep lightning-record-edit-form and lightning-input-field, you generally can't reliably disable the browser's autocomplete through the component attribute. 

If you can share which field you're trying to disable autocomplete for and what browser you're testing in, I can suggest a more specific workaround. 

Hi Ferry, this could be related to regional latency or temporary performance issues with the Salesforce Help site.  

Since you're seeing 10+ second load times consistently from Sydney, it would be useful to compare the behavior across different networks/browsers and check whether other users in the same region are experiencing it.  

If the issue is still occurring consistently, I'd recommend opening a Salesforce Support case with the affected URLs, timestamps, browser/network details, and ideally a HAR file. That will give Salesforce more information to investigate the regional performance issue. 

Hi Nisha, this can happen if there is an issue with the Classic Email Template folder page or if the required permissions aren't available.  

Please check that you have the “Manage Public Classic Email Templates” permission (or the appropriate email template management permissions) and that you have access to the Classic Email Templates folder functionality.  

Also try refreshing the page or accessing Setup → Classic Email Templates → Create New Folder again from a fresh Salesforce session.  

If the same error persists after verifying the permissions, I recommend creating a Salesforce Support case and providing the URL and exact error message, since the error itself suggests Salesforce Support investigate the page request 

@Pat Harris You have to create the flow as part of this challenge