I've one msteams bot which sends notifications to users who are on our platform. I've to change the appname(10xGoals -> PeopleCues) and logo name for this app. But when I'm trying to sideload app on a developer account on msteams, still old name is coming at some places. Old name is 10xGoals. New name is PeopleCues. Attaching pic for the reference. Where else shall I make change to reflect the PeopleCues name everywhere?
Related
I have an app that runs within Teams that shows a list of employees, name, email, presence, title and phone.
For the name column I would like to present it as a link that when clicked will open up a chat within the Teams desktop or mobile app with that employee. If there is an existing chat session, it should go to that, else create a new chat. It should not open the web client and go through the hassle of choosing to then open in the desktop app.
I was previously using this format:
https://teams.microsoft.com/l/chat/0/0?users=user#user.com
This caused the whole web client flow, so after some digging around I changed it to:
MSTeams:/l/chat/0/0?users=user#user.com
This seems to work for an existing chat but does not work for a new chat. The To: field at the top of the page is not completed.
Any ideas?
Thanks
Mar
I am sending an activity Feed notification to the user which is pointing to my personal app.
I have a DeepLink generated to point to the tab and it's working fine but when I add a SubEntuityId to the tab it is not fetched in.
It is always blank.
I have also tried with URIEncode for the same.
So presumably you're replacing APPID with the real app id from your manifest file. Separate to that, make sure that "overview" is registered as the actual entity id for the tab in the manifest. Other than that, the rest looks fine, like it should work.
I have created a Azure Bot threw bot channel registration but when i click on Setting -> (Microsoft App ID) Manage link, it always show "Not Found" page.
can any one help to resolved this issue.
There is a bug that prevents MSA accounts from navigating to their App Registration from the bot settings blade if they didn't make their own app registration when creating the bot. I am working on a fix right now, but in the mean time you can go to https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationMenuBlade/Overview/appId/{insert app id here}/isMSAApp/true or https://apps.dev.microsoft.com/#/application/{insert app id here} to manage your app registration.
July 29th edit: A fix for this has been rolled out and it should be fixed for MSA accounts.
Working on a voice bot that will take as input the voice, I have two concerns.
Technology(.net), Framework(BotFrameWork v4)
The Bot Emulator doesn't contain the recording icon, how to bring that. If by putting the microsoft app id and password, It shows up then where to get these credentials for local development and testing.
How to give the response input to the bot, v4 documentation is a way too confusing for me, I would like someone to tell me specifically what im looking for.
Thanks
You need to add your app id and password to the development endpoint in your bot file to enable the microphone feature on the emulator.
If your bot file has a production endpoint, you can likely find the app id and password there. Most bot files are encrypted, so I would recommend retrieving the id and password through the emulator. In the emulator, right click on production under the Endpoint section on the left and then select Edit Configuration. This should open a window where you can copy the app id and password.
If your bot file does not have a production endpoint and you don't have the app id and password stored somewhere else, you will have to follow this guide to register your bot on the Azure Portal.
Now that you have the app id and password for your bot, you need to add them to the development endpoint in your bot file. Once again, most bot files are encrypted, so open your bot in the BotFramework Emulator. Right click on development under the Endpoint section on the left, and select Edit Configuration. It will open a screen where you can add the Application id and password that we retrieved in the previous step.
Now run your bot and connect to it in the emulator. You should be able to use the microphone to talk to your bot. When the user talks to the bot, the emulator will convert the user's voice to text and will send the message to the bot as an activity like any other interaction the user has with the bot.
I need to create an application for another company. Therefore, I won't submit the app directly, but need to let the company customize it and submit it itself.
I heard that some attributes of the WMAppManifest.xml file are replaced automatically by the web submission interface, and others are not. What is the state of the following ones (it's never mentioned in Microsoft resources):
ProductID
Author
Publisher
PublisherID
Can I let the values generated by Visual Studio in the manifest (then I assume they will be overridden by the web submission interface), or must I ask my customer its own values for these fields?
The values of ProductID, Author, Publisher and PublisherID are only relevant for local testing and are overridden when submitting your app to the Windows Phone store...
A previous answer regarding Windows Phone 7 and the WMAppManifest.xml
Windows Phone 8 and the new PublisherID
If the other company makes the final build then it would make sense to obtain these values initially from them, so when you exchange code the data remains constant.