track-changes | compressing individual document | Cloud Storage library

I got to fix the problem by changing the ViewBag name. This issue is because of Same name for both Model and ViewBag

ModelState is composed of values from Request, ViewData/ViewBag and finally Model. Long and short, if you have a key in Request, or important to your issue here, a ViewBag member with the same name as your property, that value will be the set value for the HTML Razor generated.

Source

This could be the answer: https://developer.microsoft.com/en-us/graph/blogs/accessing-outlook-items-in-a-users-archived-shared-or-delegated-mailboxes-using-microsoft-graph/

note that such cross-mailbox API calls were never supported, and are less performant and more error-prone. (In-Place Archiving mailbox is an additional mailbox that's enabled for a user's primary mailbox.)

I believe the only alternative is using EWS.

see How to get In-Place archive mailbox in Exchange Online using Office 365 APIs

I believe this annotation is not implemented in SAP implementation of Odata, so you are out of the luck. It is supported though in ODP, but not in Gateway OData.

To enable delta tracking in OData service SAP has its own guidelines:

1. Generating delta token

2. Extend GET_ENTITYSET_DELTA method

3. First OData query on entity set will return a delta token

4. Which you then use to query delta

It turns out SYS_CHANGE_COLUMNS consists of a byte array that can be grouped into groups of 4 bytes. The more columns were changed, the longer the byte array will be, thus the more groups you can make. The first byte of each group represents an ID of a column that was changed. In all of my tests, the other 3 bytes of each group were empty (0). I assume these bytes will be used when you have a column ID larger than 255. It seems the order in which columns were changed determines the order in which they appear in the byte array. Also, the first group of 4 bytes will always be empty (0), I'm not sure why.

To use this in application code, all you need to do is get a mapping for each column name and it's respective column ID. The previous paragraph should explain how to use SYS_CHANGE_COLUMNS to determine which column ID appears in the byte array.

C# example:

It turns out you can use relationships with navigation properties on keyless entity types, just like you can with entity types.

Configure the relationship in OnModelCreating:

Same here, everything worked yesterday but today my webhook endpoint didn't even trigger once.

I think there might be an issue on Microsoft's side. I follow this issue here of someone who has the same problem as us.

UPDATE: Someone from Microsoft answered in the linked Github Issue:

There is currently an ongoing issue. The related post is TM220340 in the M365 Admin Center.

So they're confirming that the issue is on their end.