Last week was all about getting the next component for my customer into production. For one of their business lines they had some very specific requirements for a search so we built a search from scratch. Now Salesforce comes with a built in fulltext search functionality but the customer only wanted results from a specific object type and a specific record type at that. So that’s what we built. The solution was deployed on Thursday and have been running since. Main hickup in the deployment was some weird “cannot access childNodes of null” errors that kept surfacing from the Lightning component I built to display what search filters were in place. The component was basically just a wrapper around a number of arrays showing the filters as pills and showing a filter count. The markup was basically like this (c:Pill is simply a wrapper component for the pill):
{!v.filtersCount} filters added... ...</div>We kept however getting the errors and I narrowed down the issue to being with the aura:iteration components and if multiple subsequence display object arrays were being changed after one another. The fix turned out – as always – to be very simple. I simply wrapped each aura:iteration component in its own span-tag.
{!v.filtersCount} filters added... ...</div>Oh well another bug bites the dust and another lesson learned…
Besides this we got a new team member as another one of the existing team members is graduating into management. So now we also have a Salesforce Business Architect from the UK office. Nice.
What did I learn
- Span your aura:iteration components
- Troubleshooting Lightning Style
- There is a reason for having a staging environment but make sure it contains representative data…
Status after this week
Trailhead points: 85325
Trailhead badges: 100
Certifications: 5 (Salesforce Certified Administrator, Salesforce Certified Platform App Builder, Salesforce Certified Advanced Administrator, Salesforce Certified Sales Cloud Consultant, Salesforce Certified Service Cloud Consultant)Published by
