Dot Notation does not work for CosmosDb bindings

[piquet-h]

See Azure/azure-webjobs-sdk#1726

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 77fbaa31-cfcc-4b8c-abe0-4efeaee3e4f0
• Version Independent ID: db65fc3d-d8b3-1f19-91a0-4f3696fbca69
• Content: Azure Functions bindings expressions and patterns
• Content Source: articles/azure-functions/functions-bindings-expressions-patterns.md
• Service: azure-functions
• GitHub Login: @craigshoemaker
• Microsoft Alias: cshoe

[DixitArora-MSFT]

Hi @piquet-h Thanks for your feedback. We will review and update as appropriate.

[DixitArora-MSFT]

@piquet-h There is already a workaround for this discussed in GitHub issue. . This workaround was shared initially on StackOverflow. As there is a already an open issue which is been looked by Azure function product group. So the recommendation is to follow those.

[piquet-h]

That is not a workaround for this issue. It is related to the fact that nested properties are not supported. It is not related to escaping parenthesis or geospatial queries. If you look at the code that implements it, you can see that the dictionary only implements one layer deep. The dictionary should recurse if it finds a dot in the template. Get Outlook for Android<https://aka.ms/ghei36>

…

________________________________ From: DixitArora-MSFT <notifications@github.com> Sent: Wednesday, September 4, 2019 7:47:37 PM To: MicrosoftDocs/azure-docs <azure-docs@noreply.github.com> Cc: Peter Hancock <pete@freshterrain.com>; Mention <mention@noreply.github.com> Subject: Re: [MicrosoftDocs/azure-docs] Dot Notation does not work for CosmosDb bindings (#38153) @piquet-h<https://github.com/piquet-h> There is already a workaround for this discussed in GitHub issue.<#18326> . This workaround was shared initially on StackOverflow<https://stackoverflow.com/questions/44916811/difference-among-the-azure-cosmosdb-query-explorers-results-and-the-azure-funct/44918767#44918767>. As there is a already an open issue which is been looked by Azure function product group. So the recommendation is to follow those. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#38153?email_source=notifications&email_token=ADJOLKQS4G3J67NXWQIWOO3QH573TA5CNFSM4ITBEQRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD53AJOA#issuecomment-527828152>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADJOLKUXVMUL6GCHY3E3IILQH573TANCNFSM4ITBEQRA>.

[DixitArora-MSFT]

@brettsam Appreciate your inputs in this ?

[DixitArora-MSFT]

@brettsam Just following up again in case missed the previous communication.

[DixitArora-MSFT]

@piquet-h I have assigned this to content author to further review and update as appropriate.

[derekrprice]

I'm having the same problem with Queue Trigger bindings. This yields an error about "blobPath" not being defined despite the fact that I can see it in the queue message being processed.

{
  "type": "blob",
  "name": "myBlob",
  "direction": "in",
  "path": "{queueTrigger.blobPath}"
}

[craigshoemaker]

I have added a note in the article that calls out the restrictions of the dot notation.

#please-close

[meganbradley]

#please-close