Component ID's - Don't reuse

[ChTim]

Multiple times I have had the same component number/id on a popup modal as a component on the background page. When using Javascript and TB.render I end up doing things to the component on the background page that I do not want to do because it has the same component id as the component I am trying to affect in the popup modal.

If component ID’s are never repeated this would not be an issue.

[johnancheta]

Just happened to me recently and I cannot figure out why my pages were very weird. But yes, component ID’s should be unique

[Marty]

I’ve experience the same issue, and previously reported it to support. @moe any update on this?

[avromiRussell]

Auto Generate New Component ID @tim.young –

another thing to do is check for the field
if (data.record && data.record.field_740 !== undefined) – this kind of thing

[christopher93]

Hey @Marty and @johnancheta , my previous answer might be helpful for you:

Auto Generate New Component ID

@avromiRussell @moe I faced the same issue in my app. I applied a small patch in the JavaScript code. Since both the parent page and the detail popup have the same component ID, I added a unique CSS class to the parent component, and it now works perfectly as I needed. I hope this might helpfull. TB.render('YOUR_COMPONENT_ID', function(data) { if ((data.records === undefined || data.records.length === 0) && data.ele.hasClass('your-unique-class')) { data.ele.css('display', 'none');…

[Marty]

@christopher93 Thanks for sharing, that is a good idea for a workaround. I resolved my issue by recreating one of the components to force it to get a new / unique number.