function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
RubavarnanRubavarnan 

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

RubavarnanRubavarnan
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
VishhhhVishhhh
Hi team,

Any update on this??, we are also facing the same issue 
RubavarnanRubavarnan
Hi, Change the routing type to Skill based and try to deploy. U will be able to deploy.
VishhhhVishhhh
i am not using skill, i am using omni channel Queue, 
if i select Routing type as skill, i must select the skill
RubavarnanRubavarnan
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/
Rajesh3699Rajesh3699
For this issue we can make use of the data loader 
Export and Import the chat button using data loader (make sure the user is enabled as Chat User )
https://salesforce.stackexchange.com/questions/162504/include-omnichannel-routing-configurations-in-change-set

Thanks
Rajesh Adiga P.
Vinicius MariVinicius Mari
I was receiving the same message that you shared (You must select at least one skill.)
To solve this you need to leave the language on Chat Buttons & Invitations as Blank
You do not need to config skills, or activate any skills config.

liveChatAgentConfigs
<?xml version="1.0" encoding="UTF-8"?>
<LiveChatAgentConfig xmlns="http://soap.sforce.com/2006/04/metadata">
    <assignments>
        <profiles>
            <profile>admin</profile>
        </profiles>
    </assignments>
    <disableTransferConferenceGreeting>false</disableTransferConferenceGreeting>
    <enableAgentFileTransfer>true</enableAgentFileTransfer>
    <enableAgentSneakPeek>true</enableAgentSneakPeek>
    <enableAssistanceFlag>false</enableAssistanceFlag>
    <enableAutoAwayOnDecline>false</enableAutoAwayOnDecline>
    <enableAutoAwayOnPushTimeout>false</enableAutoAwayOnPushTimeout>
    <enableChatConferencing>false</enableChatConferencing>
    <enableChatMonitoring>true</enableChatMonitoring>
    <enableChatTransferToAgent>true</enableChatTransferToAgent>
    <enableChatTransferToButton>true</enableChatTransferToButton>
    <enableChatTransferToSkill>false</enableChatTransferToSkill>
    <enableLogoutSound>false</enableLogoutSound>
    <enableNotifications>true</enableNotifications>
    <enableRequestSound>true</enableRequestSound>
    <enableSneakPeek>false</enableSneakPeek>
    <enableVisitorBlocking>false</enableVisitorBlocking>
    <enableWhisperMessage>true</enableWhisperMessage>
    <label>INSERT YOURS</label>
    <supervisorDefaultButtonFilter>AgentsBemol</supervisorDefaultButtonFilter>
    <transferableButtons>
        <button>INSERT YOURS</button>
    </transferableButtons>
</LiveChatAgentConfig>

liveChatButtons
 
<?xml version="1.0" encoding="UTF-8"?>
<LiveChatButton xmlns="http://soap.sforce.com/2006/04/metadata" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <deployments/>
    <enableQueue>true</enableQueue>
    <isActive>true</isActive>
    <label>INSERT YOURS</label>
    <optionsCustomRoutingIsEnabled>false</optionsCustomRoutingIsEnabled>
    <optionsHasChasitorIdleTimeout>false</optionsHasChasitorIdleTimeout>
    <optionsHasInviteAfterAccept>false</optionsHasInviteAfterAccept>
    <optionsHasInviteAfterReject>false</optionsHasInviteAfterReject>
    <optionsHasRerouteDeclinedRequest>false</optionsHasRerouteDeclinedRequest>
    <optionsIsAutoAccept>false</optionsIsAutoAccept>
    <optionsIsInviteAutoRemove>false</optionsIsInviteAutoRemove>
    <overallQueueLength>255</overallQueueLength>
    <routingType xsi:nil="true"/>
    <type>Standard</type>
</LiveChatButton>

NO LANGUAGEUser-added imageUser-added imageUser-added image
Velvizhi RVelvizhi R
Above one didn't worked for me. Any alternate solution for this.
Prakash AcharyaPrakash Acharya
Folks, I was having the same issue. I resolved this by unchecking the "Enable queue" box in the Routing Information section of the Chat Buttons and Automated Invitations settings. For Omni-Channel as routing type, it looks like this box should not be checked.