Skip to main content

Audience support needed in Salesforce CLI

Use Case

There is a highly customized Salesforce org having Community enabled. Along with other customizations, Community is using Page Variance with the Audience. The Audience feature is used to target a set of audiences based upon defined criteria. As an Architect, I am evaluating if SFDX based Source-driven (Scratch Org based) development workflow will support Audience metadata or not.

Recap

In my previous article ExperienceBundle support in Scratch Org based (Source - driven) Development Workflow, I explained how ExperienceBundle will help in effectively versioning the metadata related to Communities and eventually another step close towards the adoption of Source-Driven development. Since ExperienceBundle supports themes, routes, brandigSets related metadata, I was under impression that Audience specific metadata will be supported too.

Audience support in Salesforce CLI

I did a small POC for this use case. I set up a Scratch Org using my repo V1.1. I created an Audience in Community Builder and did the assignment. When I tried to pull the source using SFDX: Pull Source from Default Scratch Org, Salesforce CLI gave me below error:-

No alt text provided for this imageThis error message clearly tells that Audience type metadata is still not supported by Salesforce CLI. Also, the error message suggests that Salesforce is working to close this gap.

Conclusion

If you are using the Audience feature in your Salesforce Community, it's still not supported by Salesforce CLI, so take this into consideration before making any decision about adopting Source-driven (Scratch Org based) development workflow.
The good news is that Salesforce acknowledges this gap and hopefully it will be addressed very soon. Stay tuned!

Comments

Post a Comment

Popular posts from this blog

Mashup Integration in Salesforce

During preparation for TA certification exam, I came across a word Mashup for integration a number of times. I explored about it and below is description:- Mashups, sometimes called “composites,” are hybrid applications created by bringing together several data sources and Web services to create a new application or to add value to an existing application. Behind the scenes, mashups may require different levels of integration, depending on whether the mashed-up data is only meant to be viewed, whether it can be edited, and whether data is actually transferred between systems. There are three types of mashup:- Client Presentation Mashup - In this type of mashup the integration takes place strictly at the visual level. It makes possible to view data from two or more applications in a browser,  without actually moving data between the applications. Example - Google Maps. Client Service Mashup - As mashups evolve, they are becoming more complex and sophisticated. Client ser
15 comments
Read more

Grant Access Using Hierarchies

Problem There is a custom object say 'XYZ' and OWD for this is set to ' Private ', which means record of this can be seen by only owner and users above in role-hierarchy and territory. However, to share this with other user, we can manually share it. The problem is that I don't want other users, who are above in role-hierarchy and territory of the user with whom record has shared, can see it. Solution We can un-check ' Grant Access Using Hierarchies ' check box for object 'XYZ' on 'Sharing Settings' page. We can go to Setup >> Security Controls >> Sharing Settings and click on ' Edit ' button. On the edit page, we can un-check ' Grant Access Using Hierarchies ' for required object.  Major uses of 'Grant Access Using Hierarchies' are:- If you disable the Grant Access Using Hierarchies option, sharing with a role or territory and subordinates only shares with the users directly asso
1 comment
Read more

ReadOnly Annotation

Use Case:- You want to show up to 10000 record on single VF page. Count of records based upon some business requirement where number of records could go up to 1 million. So far, it was not possible to achieve above in VF page because of following limitations:- The maximum number of items in a collection that can be iterated over using components such as <apex:dataTable> , <apex:dataList> , and <apex:repeat> is 1000. Normally, queries for a single Visualforce page request may not retrieve more than 50,000 rows. Solution:- But with API version 23.0 , salesforce has introduced ' ReadOnly ' annotation which has following functionality/restriction:- The @ReadOnly annotation allows you to perform unrestricted queries against the Force.comdatabase. All other limits still apply. It's important to note that this annotation, while removing the limit of the number of returned rows for a request, blocks you from performing the following operations
Post a Comment
Read more