This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Hello! I have a custom extension. I haven't made any changes to the code recently but today calling expandRecord() starting throwing this error and crashing my extension: TypeError: Cannot read properties of undefined (reading 'parentBase')I've confi...
A lot of my custom apps have been hanging on their loading screens for several minutes. Am I simply loading too much data (about 55 fields) from too many records (about 11,500 in the table I’m selecting with getTableByName) ? Am I using the useRecord...
Hey there! I need to create a component for one of my apps that searches through my records by a couple of criteria corresponding to fields. Is there a better way to do it than just looping thru every record and checking? I have thousands of records....
Is it better practice to pass only the values you need from the base into child components or is it okay (performance-wise) to pass down the whole record object?
For example:
function ParentComponent({record}){
const status = record.getCellValue("St...
Oftentimes my automations that include a scripting step don’t fail but also it don’t behave the way I want or expect.I want to be able to search/filter the run history of an automation based on the primary field of the record that caused the problem....
Yes, they are back to normal, thankfully! :grinning_face_with_big_eyes: Still looking forward to the potential future version of the SDK with performance improvements for large bases related to loading records! :winking_face: I did try installing...
Hi again! Yes, it is. I do have a lot of apps on one dashboard, but for most of them, the records and most of the content do not load until the viewport is expanded. I have experimented with putting each of the slower apps on their own dashboard but ...
update - I got rid of that particular error and stopped the error screens by removing the component that was referencing RecordFixtureData.commentCount (duh). not sure why that messed it up though, and it still gets stuck on the loading screen for 3 ...
