Don't suppose anyone versed with #odata could help me out with this filter? The response I am getting has dates outside of the filters, and I cannot for the life of me figure out why. Any help appreciated! #webdev #dev
https://stackoverflow.com/q/76978209/11360084

New post: OData query operations and URL encoding the system query options with curl

👉 https://qmacro.org/blog/posts/2023/08/08/odata-query-operations-and-url-encoding-the-system-query-options-with-curl/

Inspired by a comment on the thread for Task 2 of this month's SAP Developer Challenge.

#OData #curl

Share & enjoy!

Given all #REST proponents out there, it's interesting that #OData, an fully-fledged #OASIS specification is not discussed at all https://www.odata.org/getting-started/basic-tutorial/

It's a new week in the SAP Build Challenge, and this time it's all about #OData services.

Get on it! All the details in my fellow Developer Advocate @DanWroblewski's blog post 👉
https://groups.community.sap.com/t5/sap-builders-discussions/sap-build-challenge-week-4-odata-services/td-p/255954

#SAPDeveloperChallenge

If you're interested in learning more about OData and CDS annotations, and are ready for a long in-depth read, I have something for you:

"A deep dive into OData and CDS annotations"

https://qmacro.org/blog/posts/2023/03/10/a-deep-dive-into-odata-and-cds-annotations/

Share & enjoy!

#SAPCAP #OData

I was working on using OData Web API 8 to build an API, but I am getting issues where some of the routes for Get() go to the Get(id) endpoints and blow up. Taking some time away to lose the frustration. #odata

We had fun today exploring the Business Partner API (yes that's what I said) today on the live stream, if you missed it, the replay is now available complete with chapter titles for your fast forwarding pleasure. #SAPCAP, #OData, #EDMX, #curl and lots more. Share & enjoy! #HandsOnSAPDev https://youtu.be/tW0-96gGQAs

Hello #teaching bubble,

I'm currently working on a lecture focussing on modern (i.e. RAP) #ABAP programming. I want to share the development artefacts for the lecture. Currently, I'm thinking about a @GitHub repository with branches for different steps (e.g. 1st: data model, 2nd: #CDS views, 3rd: #OData service , ...).

Any thoughts about this approach? Do you have experiences in sharing lecture content this way? What are advances / disadvantages? Are there other approaches?

I’m giving #chatgpt a try, and it’s both impressive and impressively dangerous. I asked it to build an #odata server in #typescript which it did. I was amazed at first because I hadn’t really been capable of doing it myself, but it turned out that #chatgpt wasn’t either.

I think I’ll get a lot out of it, but I wish it wasn’t so confident when it is wrong. 15 years ago I’m not sure I would’ve gotten here:

@wg that being said. It sure was easy to build. I know that my past experience with 7ish years of C# development obviously helped, but the toolsets of #dotnet are also very “feature” complete.

I’d still rather do it in #Typescript to keep our small team on a single language, but it just can’t compete with the efficiency of using the #asp and #odata packages. Or maybe I can’t, but that’s the same difference for us.

@wg we did consider GraphQL, but our react client and our in-house #typescript #odata client as well as our extensive use of the BC365 APIs called for ODATA.

It’s not the only library for #dotnet or #asp that I’ve found “confusing” however. Seems like a lot of packages are still moving from “Core” to just “dotnet”. Things like why ActionResult is now prefer over IActionResult are not really explained. Even Namespaces are a mess of the new and old way in the official documentation.

@jab I can relate... I did some #OData some years ago: accessing a dynamic datamodel with OData endpoints.
Debugging the examples in the OData repo helped me with that a lot.

I feel like OData isn't getting as much love from MS as the other parts of ASP.Net b/c most people are lookig at GraphQL nowadays.

Going "old school" this weekend and working on some #OData solutions with modern ASPNET 7.

A little question for my fellow #developers. Is #OData still a thing? Personally I do like the format etc but from a little search I get the impression it seems to be a death standard?

Looking at creating the following workshops for building Web APIs in the following languages and/or frameworks:
- #OData #CSharp
- #RustLang
- #Node and #TypeScript
- #ASPNET7 #MinimalAPI #CSharp

Trying to gauge which of those would have the most interest to the community. Thank you for your feedback.🙏

Going to be rocking an oldie but still a goodie!! How about how to use the #OData protocol with ASP.NET Minimal API? That's a goal for 2023! I will be speaking and writing about it also.

Has anyone used OData and can share insights? I am leaning towards it instead of Graphql for client-driven selection and filtering.

Use case is a family of micros with _fat_ payloads. Requests are fairly coarse, so clients should just fetch the fields they're interested in. I'm avoiding standing up a middle layer BFF/Gateway, would rather let the clients hit the endpoints directly.

Ultimately, the #OData query should map 1:1 to SQL queries selecting just those fields.

#graphql #rest #odata