Skip to main content
Temas#Global Value Sets

#Global Value Sets2 debatiendo

Formular una pregunta...
Nancy Magalhaes (Marketing Administrator en Syska Hennessy Group) ha preguntado en #Salesforce Field Service
8 sept, 20:20
Convert Field using Picklist Value Sets

Hello.  

We have a field Work_Type__c picklist field on the Milestone object that references a Picklist value set. We want to instead add picklist values manually. Is this conversion possible or do I have to create a new pick list field and then add my picklist values manually? 

 

Thank you, 

Nancy  

 

#Salesforce Field Service  #Field Service Lightning  #Salesforce FIeld Service Lightning  #Global Value Sets  #Salesforce Admin  #Salesforce  #Salesforceadmins  #Systems Administrator

1 respuesta
  1. Daniel Cartwright (Broadridge)
    8 sept, 21:18

    Hi Nancy, 

     

    No, once you've made a picklist field with global values, it can't be changed to a custom picklist. 

     

    I think you're right and you'll need to create a new picklist field with custom values. 

     

    Hope this helps, 

    Dan

Escribir una respuesta...
0/9000
Andrey Shestakov (Business & Technology Delivery Team Lead en Accenture) ha preguntado en Salesforce DX
13 oct 2022, 13:38
Namespaced (FSC) GlobalValueSetTranslation Metadata - Translations Entered in Translation Workbench Not Retrieved

To reproduce issue with retrieve:

0. FSC package installed in an org.

1. Go to Setup -> Translation Workbench -> select Language and Setup Component = Global Value Set

2. Enter Value Label Translation for a 1+ Countries and/or Languages

3. Save the changes

4. Retrieve GlobalValueSetTranslation metadata components with API 55.0 (e.g. via package.xml and VS Code):

Finserv__Countries

Finserv__Languages

5. The components are retrieved, but don't contain the translation values (value in <translation></translation> is still commented as by default) that were entered in the Translation Worbench.

 

Expected result:

1. Changes done and saved in Translation Workbench are reflected in the .globalValueSetTranslation-meta.xml when retrieved

 

Current workaround:

1. Retrieve GlobalValueSetTranslation metadata components

2. Update translations as necessary in the .globalValueSetTranslation-meta.xml file(s)

3. Deploy the files into required orgs.

4. Changes done in xml files are deployed correctly.

 

Extra notes:

1. Translation entered via the workaround are retrievable, but translations entered via Translation Workbench are not.

#Metadata API #Global Value Sets #Translation Workbench

2 respuestas
Escribir una respuesta...
0/9000
David Huddleston (Sr. IT Business Partner en Honeywell UOP)
28 sept 2021, 17:46
Promoting Standard Picklist Fields to a Picklist Value Set (Global Picklist)

Hi Folks, I am hoping someone has an answer out there.  I am wanting to promote the "Product Family" from the Product object to a Picklist Value Set.  Everything, I'm reading states you cannot do this first it is not restricted and second it is a standard picklist so they cannot be promoted.  However, I'm trying to get my company to work with standard fields where ever possible and rather than use Product Lines we are currently using Product Family.  That is all good and well, however, when I want to us the Product Family on other objects that means I have to create a separate Picklist Value Set and maintain both.  

 

I like to work on the beer truck theory here (Thanks Harry), if I get hit by a beer truck on my way to work someone needs to be able to come in and pickup where I left off.  Having to remember multiple picklist update locations is a relic from the pre-Global Picklist days.  I am hoping someone has a recommended solution.  I did find an app to help convert picklists to global picklist that was created by Salesforce Labs (Vladimir Gerasimov), however, that requires the picklist value to be a "Restricted" list as well and I can't make the Family filed a restricted picklist value.

 

Any advise is greatly welcome.  Hoping this is on the future scope almost as much as I'm hoping Dynamic Pages will come to standard objects.  

 

#Global Picklists  #Global Value Sets  #Sales Cloud

2 respuestas
  1. David Huddleston (Honeywell UOP)
    28 sept 2021, 18:35
    Thank you Ambon, that was my fear I was more looking to use the family field from the products in other objects. I do like the flow idea, it just seems to go against the grain of the AWESOME Global Picklists. (Picklist Value Sets). Well if Salesforce is listening this would be really awesome if you could allow standard picklist to be promoted to picklist value sets.
Escribir una respuesta...
0/9000
Corrina Cohen (Digital Marketing Manager en Bio-Techne) ha publicado en * Trailhead Official *
17 oct 2017, 16:06

I am working on the Picklist Administration - Share Values with Global Value Sets and when i got to check my work for the Hands-On challenge I keep getting this error: 

"There was an unhandled exception. Please reference ID: OQNFGQPM. Error: Faraday::ClientError. Message: MALFORMED_QUERY: When retrieving results with Metadata or FullName fields, the query qualifications must specify no more than one row for retrieval. Result size: 3"

 

I did not write a query as part of this challenge so the error has me confused. 

4 comentarios
  1. Chris Duarte (Salesforce)
    19 oct 2017, 2:45

    The issue is that you've set up more than 1 picklist value. We're fixing the code in the next couple of weeks so that it will allow you to have more than 1. But that's why the error is telling you your result size: 3 -- it wants to find 1 and it's finding 3.

    If you remove the other 2 or redo this in a new playground with just 1 value, you should be able to pass.

    My apologies for this trouble.

Escribir un comentario...
0/9000