05-24-2023 05:23 AM
Hello,
Your documentation states that it's not possible to update a message containing an attachment (Adaptive Card).
https://developer.webex.com/docs/api/v1/messages/edit-a-message
"Edits of messages containing files or attachments are not currently supported. If a user attempts to edit a message containing files or attachments a 400 Bad Request will be returned by the API with a message stating that the feature is currently unsupported."
Your sample page doesn't have the attachment field to edit the card. BUT when I try to update the message using Postman I can PUT and update the Adaptive Card. It seems to be working great.
In the end, do you officially support the update of an Adaptive Card and the documentation is not updated?
Thanks
Solved! Go to Solution.
05-26-2023 12:49 AM
Hi @dupontb,
Thanks for your patience so far!
We discussed this topic internally with Cards Engg. as well as with the Product.
So, one thing I just wanted to clear at the very beginning (as I learnt from the internal discussion) that in this case we're updating just the Card Text actually and that should not be considered as the update of the whole attachment or, files!
And this type of small attachment update/s is currently possible only for a few attempts, which means if we try to update a Card N-number of times - at some point it'll start throwing error.
Also, only if the Card attachment doesn't have any Image in it, then the Card Text update is still possible.
But in case the Card has an Image along with Texts, then updating that Card Image or, even Card Text would be impossible starting from the first attempt and it'd throw the below error -
{
"message": "Support for editing messages with files via Developer APIs currently disabled",
"errors": [
{
"description": "Support for editing messages with files via Developer APIs currently disabled"
}
],
"trackingId": "ROUTER_XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX"
}
And, the same has been documented as well here - https://developer.webex.com/docs/buttons-and-cards#limitations
Please check the last point under Limitations section.
Hope this helps here to understand the complete background of it.
Regards!
Sandip
Please Note: If you think the solution provided above was helpful and satisfactory, please accept it as a Solution! However if you want to discuss it further and get yourself unblocked, please don't hesitate to reply back on this thread and we'll try to answer those queries by the soonest. In that case, once all of your queries are cleared - finally you can mark it as "Accepted as Solution"
05-24-2023 07:00 PM
That's a beautiful catch @dupontb !
I tested the same and was able to successfully update the Card JSON from Postman as well.
Let me check with our Backend team on this, will get back to you.
Regards!
Sandip
05-26-2023 12:49 AM
Hi @dupontb,
Thanks for your patience so far!
We discussed this topic internally with Cards Engg. as well as with the Product.
So, one thing I just wanted to clear at the very beginning (as I learnt from the internal discussion) that in this case we're updating just the Card Text actually and that should not be considered as the update of the whole attachment or, files!
And this type of small attachment update/s is currently possible only for a few attempts, which means if we try to update a Card N-number of times - at some point it'll start throwing error.
Also, only if the Card attachment doesn't have any Image in it, then the Card Text update is still possible.
But in case the Card has an Image along with Texts, then updating that Card Image or, even Card Text would be impossible starting from the first attempt and it'd throw the below error -
{
"message": "Support for editing messages with files via Developer APIs currently disabled",
"errors": [
{
"description": "Support for editing messages with files via Developer APIs currently disabled"
}
],
"trackingId": "ROUTER_XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX"
}
And, the same has been documented as well here - https://developer.webex.com/docs/buttons-and-cards#limitations
Please check the last point under Limitations section.
Hope this helps here to understand the complete background of it.
Regards!
Sandip
Please Note: If you think the solution provided above was helpful and satisfactory, please accept it as a Solution! However if you want to discuss it further and get yourself unblocked, please don't hesitate to reply back on this thread and we'll try to answer those queries by the soonest. In that case, once all of your queries are cleared - finally you can mark it as "Accepted as Solution"
01-10-2025 01:38 PM
Hello,
I'm also running into a problem with this. I can update the card as expected, but afterwards the action buttons in the card no longer work. The web client actually shows a short error message ("Unable to send your request") and in the browser development tools I see the following:
{
"errorCode": 1400103,
"message": "Parent activity has been deleted",
"errors": [
{
"errorCode": 1400103,
"description": "Parent activity has been deleted"
}
],
"trackingId": "webex-web-client_a55196a8-8c96-4892-80e5-6278ef4de3df_673"
}
My use case is to have the card updated after a user interaction but still give the user the ability to trigger another action from the same card afterwards. The limitations you linked do not address this. There I only find the following:
Editing of Cards on User interaction is possible only for cards with no images, pre or post Edit.
01-14-2025 11:58 PM
Hi @Martin K,
Just to update, we had a couple of discussions over this topic recently regarding Card content edit in case of Webex Card message and what has come out of that discussion is, the Webex Card text or, content is still not very accurate for editing.
It's glitchy as well as at times based on which OS we're performing the operation like Windows or, OS, it depends. But it's true that Card edit operation is still not very smooth and it's not yet fully supported.
Also, if the Card has some images or, Action button and if the Card is edited - then such images on Card or, action button performance might impact.
Only in case of text content based Card, it should still work fine. Hope this helps!
Therefore, since this operation of Card Edit with an Action.submit Button in it doesn't still supported by the Card Engg. team themselves, so we're not extending this item for Engg. discussion internally further.
But if you've any further queries - please let us know.
Regards!
Sandip
01-15-2025 09:19 AM
Sandip,
I appreciate the reply. I get the feeling that the Adaptive Card support is not very high on the priority list. Supported version is 1.3 (whereas current version is 1.6), update of cards is not supported and sending the data along with a template is also not supported. This might not be the best place to ask this question, but what is the roadmap regarding Adaptive Card support in Webex?
01-15-2025 09:40 PM
Thanks @Martin K for the follow up!
Yes, Button & Cards Engg. team has planned to upgrade the Card version with further releases only based on the discovery or, expose of specific capabilities on top of the existing ones.
They're not going to release further Webex Card versions based upon the current version i.e., 1.6
So, this is a specific approach they're currently following and we also asked very recently if there is any upcoming plan/roadmap for Card v1.4 release, but unfortunately we don't have a ETA from them.
05-26-2023 03:57 AM
For my use case, I display a card with an input and I update it with an error message when needed.
It's a basic case you are supporting at the moment.
Thanks for your help
05-28-2023 09:21 PM
Hi @dupontb,
Yes, as you shared the background, that should not be a problem as of now to update your Card's content as per the current logic/behaviour.
But we wanted to share the complete background from our so it gives you a clear picture and doesn't make confusion later in case you try to implement further updates on the Card.
Please let us know for any further assistance!
Regards!
Sandip
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide