+ Start a Discussion

Deployment error : You must select at least one skill

Dear Folks,

Facing an error while deploying Chat Button. Routing type is Omni channel queues. But the error is showing related to Skill.
Routing type is Omni channel queues

What am i missing?
SFDC Prime SquadSFDC Prime Squad

Hi Rubavarnan,

You need to create skills and assign these skills to the chat button for deployment.
Please refer this link for details: https://help.salesforce.com/articleView?id=live_agent_create_buttons.htm&type=5

Hello SFDC Prime Squad,

Thats true. But i am using Omni channel queue as a routing type. So We will be assigning the queue directly in chat button.

FYI. Chat buttons with Skill based routing, I am able to deploy. But I changed the routing type from Most available to Omni channel queues (To use Live Agent in Lightning Experience)

User-added image

If you see the screenshot, routing type is Omni channel Queues and the queue assigned below.
sampath Kumar 177sampath Kumar 177
even i am facing same issue i configer it from Omni Channel Queue. but while trying to deploy i am getting error as "You must select at least one skill" . Please help me
Hi team,

Any update on this??, we are also facing the same issue 
Hi, Change the routing type to Skill based and try to deploy. U will be able to deploy.
i am not using skill, i am using omni channel Queue, 
if i select Routing type as skill, i must select the skill
Yes.. You are right. Just Create one skill and add it to the chat button. Then do deploy. After that, change the routing type to omni in destination environment. I know it's not a good way. But that's how we have overcome it.
Gerardo VillasenorGerardo Villasenor
Per this page: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_livechatbutton.htm

"Chats routed with Omni-Channel aren’t supported in the Metadata API."

If you retrieve the metadata using VS Code or Ant, the routingType tag is empty if you try to use Omni-Channel Queue/Skills option. If you select one of the other values you will see a valid value in tag (Choice, LeastActive, MostAvailable).

I'm having same issue here but did a test using one of those three valid values and then I was able to clear that error when I did the validation. Wonder if this is something Salesforce will fix on a future release, for now I think the only way is follow Rubavaman's suggestion. I'm not happy with that workaround either as we depend of someone in Production to make the change after the deploy as an extra step but at least it allows me to continue working for now.
David HideDavid Hide
Thanks a lot Gerardo! Per this page: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_livechatbutton.htm
Wors for me perfectly, I just had exactly the same issue in my working project site https://eduloh.com/99papers-com-review/