Azure function is not working after upgrading WebJobs.Extensions.CosmosDB and WebJobs.Extensions to the latest versions

Question

Azure function is not working after upgrading WebJobs.Extensions.CosmosDB and WebJobs.Extensions to the latest versions

lakshmi 816

Based on the below reference document we have done the changes for the latest version of Cosmos DB extension.

https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/migrate-dotnet-v3?tabs=dotnet-v3#major-name-changes-from-v2-sdk-to-v3-sdk

But still we are seeing error for the below cases,

=> In that article it also mentioned that "Document is renamed to Item" , I tried the same and it was showing error.

=>Table attribute also didnt worked saying "Could not found , are you missing some directive or assembly reference". Based on the below links, installed "Microsoft.Azure.WebJobs.Extensions.Tables" and the error in Table attribute has removed.

https://learn.microsoft.com/en-us/answers/questions/607702/microsoftazurewebjobsextensionsstorage-500-and-tab.html

https://github.com/Azure/azure-sdk-for-net/issues/25342

=> In Document client we had "DeleteDocumentAsync" for deleting the document . In Cosmos client , should we need to use the below method for document deletion,

Also we have removed the deprecated package " Microsoft.Azure.Cosmos.Table" and added " Azure.Data.Tables" .

In the below link , it has mentioned about TableClient which can be used in same place of Document client

https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.Tables/1.0.0

Can you please help to confirm which client needs to be used when using " Azure.Data.Tables" and "Microsoft.Azure.WebJobs.Extensions.Tables" packages

lakshmi 816 Reputation points

2023-01-03T11:16:13.173+00:00

Can anyone help on this issue,

We are still blocked with the azure function upgrade. Based on the article we have renamed Document to Item , but still its showing as name space doesnt exists
MuthuKumaranMurugaachari-MSFT 22,441 Reputation points Moderator

2023-01-04T16:05:33.51+00:00

@lakshmi Thank you for reaching out to Microsoft Q&A. Sorry for the delay in response. Based on my understanding, you were able to resolve issue: "Could not found , are you missing some directive or assembly reference" by installing Microsoft.Azure.WebJobs.Extensions.Tables and faced an issue using new type Item. Is that correct?

When using Microsoft.Azure.WebJobs.Extensions.Tables package, you can use TableClient and refer usage samples here. It seems like you are also adding Azure.Data.Tables library to directly interact with Tables service. Have you already checked Migration guide?

Can you share function extension version, package reference info, code snippet along with the full error message? That would really help in understanding the issue better. Feel free to add a comment for any additional questions.
lakshmi 816 Reputation points

2023-01-05T08:23:16.027+00:00

Yes , Error in Table attribute has removed with installing Microsoft.Azure.WebJobs.Extensions.Tables .

Now I have replaced cosmos client with Table client. Below is the code snippet,

Still i am seeing error in Document and also in deleting the document

Accepted answer

0 additional answers

Your answer

lakshmi 816 Reputation points

2023-01-03T11:16:13.173+00:00

Can anyone help on this issue,

We are still blocked with the azure function upgrade. Based on the article we have renamed Document to Item , but still its showing as name space doesnt exists
MuthuKumaranMurugaachari-MSFT 22,441 Reputation points Moderator

2023-01-04T16:05:33.51+00:00

@lakshmi Thank you for reaching out to Microsoft Q&A. Sorry for the delay in response. Based on my understanding, you were able to resolve issue: "Could not found , are you missing some directive or assembly reference" by installing Microsoft.Azure.WebJobs.Extensions.Tables and faced an issue using new type Item. Is that correct?

When using Microsoft.Azure.WebJobs.Extensions.Tables package, you can use TableClient and refer usage samples here. It seems like you are also adding Azure.Data.Tables library to directly interact with Tables service. Have you already checked Migration guide?

Can you share function extension version, package reference info, code snippet along with the full error message? That would really help in understanding the issue better. Feel free to add a comment for any additional questions.
lakshmi 816 Reputation points

2023-01-05T08:23:16.027+00:00

Yes , Error in Table attribute has removed with installing Microsoft.Azure.WebJobs.Extensions.Tables .

Now I have replaced cosmos client with Table client. Below is the code snippet,

Still i am seeing error in Document and also in deleting the document

Answer 1

@lakshmi Thank you for sharing the code snippet. Based on your reference on Azure Cosmos DB .NET SDK v3, I assume you are using Microsoft.Azure.WebJobs.Extensions.CosmosDB with version 4.0.0 (which implements referenced SDK #717).

As described in docs, there is no direct replacement for Document type and the recommendation is to use C# type instead of generic types. There are lot of samples about Usage in the SDK repo reference and ItemsManagement sample has all operations such as read items, create item, delete item, etc. that you might find it helpful (the example used SalesOrder type).

The below description refers to the naming convention and will pass on the feedback to our doc's team since this might cause small confusion.

Document is renamed to Item

Also, want to let you know that Microsoft.Azure.WebJobs.Extensions.CosmosDB extension uses Microsoft.Azure.Cosmos library (refer NuGet) whereas Microsoft.Azure.WebJobs.Extensions.Tables extension uses new library Azure.Data.Tables (refer NuGet). I see there is another thread being discussed about this with Cosmos experts and feel free to post there for any specific questions about Cosmos library (refer Guidance)

I hope this answers your question and feel free to add a comment if you have any other questions. We would be happy to assist you. Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community.

lakshmi 816 Reputation points

2023-01-06T16:17:49.19+00:00

We are developing a chat bot. For Azure functions , we are using Cosmos DB trigger which needs Microsoft.Azure.Cosmos.

In interfaces which is used in Azure function has changed from Cosmos table to Azure.Data.Tables.

So , will this create any issue in azure functions.

Azure function :

Table Provider contains the method to access the repository using table client and Agent Log entity is the interface .
MuthuKumaranMurugaachari-MSFT 22,441 Reputation points Moderator

2023-01-06T16:34:39.623+00:00

@lakshmi Tagging Cosmos DB in this thread to answer this question. Both are client libraries and I doubt if this would cause any issue. But I would recommend starting a new thread with Cosmos DB experts since this question would greatly help on others in the community as well.

Share via

Azure function is not working after upgrading WebJobs.Extensions.CosmosDB and WebJobs.Extensions to the latest versions

0 additional answers

Your answer