TypeError: Cannot read property 'setAttribute' of undefined

Hello, I've been having this error for some time and searching isn't helping me. Can someone take a look at the error?

OS 11

SS Version 11.7.4

Reactive Web App

Logger.js:446 [2020-04-30T]: Cannot read property 'setAttribute' of undefined
TypeError: Cannot read property 'setAttribute' of undefined
    at t.e.setDataHeaderInRowCells (https://AddressHere/ModuleNameHere/scripts/OutSystemsReactWidgets.js?g6vLwSDRVhefYXu4a3zEGw:2:10522)
    at t.e.componentDidUpdate (https://AddressHere/ModuleNameHere/scripts/OutSystemsReactWidgets.js?g6vLwSDRVhefYXu4a3zEGw:2:10674)
    at t.internalComponentDidUpdate (https://AddressHere/ModuleNameHere/scripts/OutSystemsReactView.js?xVGq_92hjirKl1JjLw3Ktg:9:3164)
    at t.e.<computed> (https://AddressHere/ModuleNameHere/scripts/OutSystems.js?PGHrEBzLHyLxW9cX_pLDCA:9:21997)
    at t.o (https://AddressHere/ModuleNameHere/scripts/OutSystemsReactView.js?xVGq_92hjirKl1JjLw3Ktg:8:26407)
    at t.e.<computed> [as componentDidUpdate] (https://AddressHere/ModuleNameHere/scripts/OutSystems.js?PGHrEBzLHyLxW9cX_pLDCA:9:21997)
    at r.notifyAll (https://AddressHere/ModuleNameHere/scripts/OutSystemsReactView.js?xVGq_92hjirKl1JjLw3Ktg:1:6756)
    at r.close (https://AddressHere/ModuleNameHere/scripts/OutSystemsReactView.js?xVGq_92hjirKl1JjLw3Ktg:4:8393)
    at r.closeAll (https://AddressHere/ModuleNameHere/scripts/OutSystemsReactView.js?xVGq_92hjirKl1JjLw3Ktg:5:10699)
    at r.perform (https://AddressHere/ModuleNameHere/scripts/OutSystemsReactView.js?xVGq_92hjirKl1JjLw3Ktg:5:10145)

Thanks in advance for taking a look!

HI Joaquim Mauricio,

Can you describe more ,where are you getting this error like where are you using JS or widgets.

Regards

Rahul Sahu

Joaquim Mauricio wrote:

Hi Joaquim, can you give us more context? what are you doing when appearing this error, which component? or upload the oml, thanks

This happens right after the page loads, and I can't figure out exactly where this is coming from.

It's a page that is very heavy with web blocks containing tables, and I am not using any external JS.

Can't upload OML...

HI Joaquim Mauricio,

you are using some rich widgets in your page or block.i think you need to check  property of Property of Rich Widget component which you are using.

provide some images of blocks and codes also

Regards

Rahul Sahu

After some more debugging (on firefox dev edition, it showed different and more specific errors), it was due to a table in a web block that had an empty header. For some reason this was throwing me a javascript error, are the tables completly generated in javascript?

Thanks for your help guys.

Hi Joaquim Mauricio,

I am also getting the same error. In the scenario, table in the webblock is accessed in  the parent screen table.

Did you solved the error ?

Any suggestions recommended

Regards,

Ellakkiya.s

Hi Joaquim and Ellakkiya,

For Mobile and Reactive Web applications, the entire application is generated via JavaScript on the client-side.

Was the column with the empty header configured to have sorting as well? Without knowing the details of how that is implemented, I'd suspect that could be a potential issue.

Hope this helps!

Joaquim Mauricio wrote:

You are setting/using some values of an element where that element does not exist.

you need to look into your JS section all the element loaded successfully before calling it

Hi Jorge  and Salman Ansari,

Thankyou for your replies,

In my application there is no empty header. still i am receiving the same error.

can you please  look into the attached oml

Hello Joaquim Mauricio and Ellakkiya Selvadurai, thank you for reaching out.

I've looked into the oml provided by Ellakkiya Selvadurai and there seems to be an issue with nested tables for the platform's Table Records widget in Reactive applications.

If possible, Joaquim Mauricio could you submit a report in Service Studio through Help -> Give Us Feedback so that we can analyse the oml and make sure it's the same pattern that's causing the error?

I apologize for the inconvenience, we'll be looking into this issue.