We are building out a community on the Partner Central template. We are using Salesforce DX and scratch orgs, and we’ve also taken the time to use the skuid-grunt tool from NPM to help get our Skuid pages into source control.

We’re using the Skuid Lightning Component in the builder, and the page appears. But we’re finding some confusing behaviour - I’ll use the latest example we’ve had of the problem.

I wrote a custom field renderer to show a contact’s Name, Email, and Phone number in a field, rather than just their name (template fields don’t work in the Community - I’ll post about that separately!).

The Customer changed their minds, so a colleague of mine took out the bit of the Javascript snippet that added the phone and email address. He pulled the page and put it into source control; I pushed it into an org. In the Community, the old version of the page continued to show - I could still see the email and phone number. Running the page internally (launching from within LEX), I got the new version. I made a small change to the page - literally, just added a space to a page editor header, saved, and I started to see the correct version of the page.

Now as I’m writing this I realise that I pushed the pages to the same org my colleague changed the page in and pulled them from… but I think that’s a red herring, My thoughts are either an issue with Skuid caching in a Community, or maybe the skuid-grunt tool?