-Make sure the {{Account_Name__c}} & {Account__c}} fields are added to your model -Make sure you have permissions to view those fields in Salesforce -I’ve never to had to do this before for a url, but worse case maybe you need to point to the model + field. If so u can try this syntax: {{$Model.YOURMODELNAME.data.0.Account__c}} Hope it helps
Fields included in model - check.
Permssions to view fields - check.
I tried the syntax you suggested, but got the same results – Still no merge field values.
I did get a small improvement using {{$Param.id}} instead of {{Account__c}}. I tried hard coding the account name along with the Param.id just as a test and it still failed:
When side by side testing (visualforce called from standard vs skuid), the error above persisted until I changed the domain prefix from:
mydomain–skuid
to
mydomain–c
So while I’m still not getting {{Account__name__c}} to show up in the URL, I have a very different challenge ahead as well.
You may want to start with the URL above and then add parameters one by one while troubleshooting along the way.
The other thing you will want to try is a triple mustache for the parameters. Instead of {{Account__c}} change it to {{{Account__c}}}. This ensures that you get ‘just’ the value and not a hyperlink. With a double mustache on a lookup field, Skuid will try to render the hyperlink instead of passing in the ‘id’ that you want.
To get a relative link from a skuid page to a standard vf page you can use syntax like this: /apex/c__visualforcePage This means that the page will be sourced from the visualforce namespace (and the initial part of the URL will be correct) and the skuid namespace will be ignored. Again the key is “c__” before the vf page name.