When deploying Salesforce-related metadata, configured on a French Org, have you already met this strange error : « Error parsing file: ‘ ‘ is not a valid value for the enum ‘Gender' » ?

In fact all langages, with gender for their nouns, are possibly concerned.

That means that you could face this issue, if you are deploying metadata, between unrelated instances, from an organisation whose langage is gender-oriented, towards an organization whose langage is not.

As a workaround, please go to the metadata repository, which contains your instance codebase.

In this case, to solve this issue, I have edited the CustomObjectTranslation raw file, from within the code repository, removed the following gender line, and then committed the modified file in the same branch.

<gender> <!-- Feminine --></gender>

Then, within Gearset – but it would be the same with GitHub Actions – please refresh your metadata comparaison to update the file content from your selection, and validate again for deployment. This time, it should be ok, and you should not cope with this error anymore.

To read more on the subject :

• Resolving validation errors – « Cannot specify a gender for a gender neutral language »: https://docs.gearset.com/en/articles/5646773-resolving-validation-errors-cannot-specify-a-gender-for-a-gender-neutral-language
• CustomObjectTranslation reference page in Salesforce help: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_customobjecttranslation.htm

If you have ever met this kind of deployment error

Error SOM_990_Manual_Shipment FOLI_to_Ship_Section1 (Screen Component) - Because the "FOLI_to_Ship_Section1" screen field on the "FOLI_to_Ship" screen is a section, the regionContainerType is required. 

That comes from missing information from within deployed flows.

When you see this error, that means that a regionContainerType tag (added in Salesforce flow metadata description in a previous release : v55.0) from a flow’s field metadata component is missing.

To avoid these deployment errors, you shall edit your flow within your code repository, to add, after each RegionContainer definition line, the following tag :

<regionContainerType>SectionWithoutHeader</regionContainerType>

Here is the result of the text edition, in the flow-related raw file, seen, modified and then committed, directly from within GitHub repository

After changing the flow content, the deployment is then validated by Salesforce

To whom may wonder how to share a same list view to a certain group of users, you should leverage Public Groups.

When creating a list view in Salesforce, you can create it :

• for your own
• for all users (you cannot be too selective on your filters, on a wide-open list view)
• for a set of users from within roles / roles and subordinates

However, when you do want to share a list with a limited number of users, from the same role for example, you could feel that you should need to create a subrole just for it, or open it up to all users because you think you cannot do any other way.

To be able to target a list of specific users, you could leverage Public Groups

To do so, navigate to Setup > Public Groups > New, create a public group with a relevant name, that would be easy to understand for users who would need to share their list views.

Once done, you will see that you are now able to share list views with Groups ; this option is now available among the list sharing options :

Here, we share the new list view, with the newly created Public Group :

To read more on the subject :

• Salesforce Help article : https://help.salesforce.com/s/articleView?id=sf.ls_create_public_groups.htm&type=5
• Create a list view :
• Work with List Views in Lightning Experience : https://help.salesforce.com/s/articleView?id=sf.basics_understanding_list_views_lex.htm&language=en_US&type=5
• List View-related Trailhead unit : https://trailhead.salesforce.com/content/learn/modules/lex_customization/lex_customization_list