Skip to main content
Nintex Community Menu Bar

Here is what I am doing:

I have a very basic form for Agents to submit their property listings with us. They have to select their Agency, then it allows them to select their Agent name (both are pulled from our Account & Contacts in Salesforce).

I have two lookup filters on the ‘Agent Name’ field - The first filter makes sure it only returns the Agents that are related to the Agency (selected in Dropdown above). The second, is a custom ‘Active’ field I use to determine if that Agent is still active. When this is not checked, they should not show up in the ‘Agency Contact’ field (see pic):

 

The strange part: This works perfectly when I preview the form. However, when I save and test on the published page, it just wont work - driving me crazy.. Please help!!!

Regards


Alex

Hi @awebsterx. Interesting. I have some recommendations and, if they don’t work, two questions.

Recommendations

  1. For your lookup filter on the AccountId field, use the Account__c field. (This field already contains the Id value).  Using Account__r.Id will be less performant because it has to reach into the related object.
  2. Make sure that Account__c field and the Status__c field that you’re using for these filters are included in your model.

Questions

  1.  What version of Skuid are you using?
  2. Where are you publishing your page?

Hi Anna

Thanks so much for betting back to me.

I'm using Skuid version 16.4.4

I publish to a visualforce page that is assigned to a custom site domain on Salesforce.

Note: I tried your suggestion above (adding status_c to the model) and it still persists.

Regards


Alex


Hi Alex,

  1. Did you also try changing your lookup condition to be on the Account__c field? Please try this if you haven’t already.
  2. If #1 doesn’t work, is there a permissions difference between your user and the site user? Make sure the site user has access to all the records and fields (including on the related object).


Custom Site best practices:

  1. Make sure you’re using the skuid:page component in your Visualforce page.
  2. Docs: Deploy in a Force.com site - Final Checklist.  There are also docs about Experience Cloud if you’re going that route.

@annajosephine Thanks so much for pointing me in the right direction!

It was a field permission issue on the site user profile that required ‘read’ access.

Regards
Alex


Reply