Error creating event - The property 'address' does not exist - microsoft-graph-api

Just started repeatedly getting this error, with the same request structure the app was successfully using before to create an event using the Microsoft Graph API -
"The property 'address' does not exist on type 'Microsoft.OutlookServices.EmailAddress'. Make sure to only use property names that are defined by the type or mark the type as open type."
The "attendees" property of the failing request looks like the following:
"attendees":[{"emailAddress":{"address":"emailaddress#host.com"},"type":"required"}]
Any help would be greatly appreciated.

Related

Can't add description to OneDrive folders

I'm posting a create item http request the to the graph api ("\children") to create a folder under a groups files, but I'm getting the following error:
"code": "-1, Microsoft.SharePoint.Client.InvalidClientQueryException",
"message": "The property 'description' does not exist on type 'oneDrive.item'.
Make sure to only use property names that are defined by the type."
It does not allow description to be part of the the request body json, even though the documentation says it is a read-write property on the item type.
Please help anyone!?:) The description field could be really valuable to store additional info about a folder or file.
The description property isn't support for OneDrive for Business right now, which is why this call fails. If you create a folder without the description property the call should succeed. I've made updates to the documentation to remove the description property from the docs until it's supported for OneDrive for Business.

Breeze with second controller

I need to get some data from a different database (different server, actually), so I've created a second datacontext pointing to a second Breeze controller, repository, and edmx. I also created second model and entityManagerFactory since data I'll need to be getting is substantial and wanted to separate it from the base functionality. In my new EntityManagerFactory, if I have:
breeze.NamingConvention.none.setAsDefault();
all works well, but I don't get camel casing. If I have:
breeze.NamingConvention.camelCase.setAsDefault();
or if I don't call it at all (since it's just setting the app-wide default which is already set) I get this error:
[myDatacontext] [HT Error] Error retrieving dataMetadata query failed for: breeze/Vsp/Metadata. Unable to either parse or import metadata: NamingConvention for this server property name does not roundtrip properly:name-->Name; [object Object]Error: Metadata query failed for: breeze/Vsp/Metadata. Unable to either parse or import metadata: NamingConvention for this server property name does not roundtrip properly:name-->Name; [object Object]
There's not even a "name" or "Name" property on class I'm getting.
What am I missing?
By the way, I do get the metadata from the server. The client just doesn't like it.
I suppose that since you've posted this you found a solution.
But I also had this problem, it is because I use Entity-Framework ADO .Net 6.0, it takes into account stored procedure, views or tables that are not camelcase, so you have to unselect them before generating the model / context.

Custom error message in message.properties

I've got Form domain class and there is typeOfTransaction property. This property is required (blank: false). I want to write custom error message for this property, if the user does not set the value, the message must be appeared.
com.example.domain.form.typeOfTransaction.blank = Type of transaction required
Above is the message, but I don't get it when I'm trying to save form with empty typeOfTransaction field. Instead of this message I've got default message
"Please select an item in the list."
p.s. I don't know where this default message is defined.
If you use the absolute name of your class you need to use the exact name of the class, including capitalization - so I'm guessing you should put:
com.example.domain.Form.typeOfTransaction.blank = Type of transaction required
If you don't use the absolute name you don't capitalize the class name:
form.typeOfTransaction.blank = Type of transaction required
Well, for 1.3.7 it should be in grails-app/i18n/messages.properties (or one of the language specific variants if appropriate). I assume 2.0 would use the same location.

EPL Errors with Nesper Patterns

I am experimenting with Nesper (.NET version of Esper) and ran into a few troubles that I just cannot understand. The following simple EPL (modeled after the tutorial) fails with an error:
select * from pattern [every (e1=SeenEvent -> e2=SeenEvent(ID=e1.ID))
where timer:within(1 min)]
The error I get is:
Property named 'ID' is not valid in any stream
My first suspect was the ID may not be exposed correctly in the SeenEvent class which derives from Observation class. But I confirmed that in Observation class property ID is defined as Public.
Is this a known issue with EPL? Is Nesper different from Esper (it's Java cousin)?
You could try "select ID from SeenEvent" to confirm whether "ID" is actually exposed. The property names are case-sensitive, try "id" as well. Rename the property may also help.

MVC Model Error on TryUpdateModel()

I have an error (see below). At first glance it seems obvious to me, however. I've checked everything: the MODEL is ok; metadata class set ok and i've checked my controller and at the time 'TryUpdateMOdel' is called all is well and the object is as i expect it to be. I'm thinking this will be something silly but been stuck all day, anyone recommend anything?
The associated metadata type for type 'Lms.Model.PaymentFrequency' contains the following unknown properties or fields: SiteAgreementId, PaymentTypeId, PaymentCategoryId, ObligationStartDate, TerminationDate, Comments. Please make sure that the names of these members match the names of the properties on the main type.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.InvalidOperationException: The associated metadata type for type 'Lms.Model.PaymentFrequency' contains the following unknown properties or fields: SiteAgreementId, PaymentTypeId, PaymentCategoryId, ObligationStartDate, TerminationDate, Comments. Please make sure that the names of these members match the names of the properties on the main type.
Source Error:
Line 120: PaymentFrequency paymentFrequency = this._siteRepository.GetPayment(Convert.ToInt16(collection["PaymentId"])).PaymentFrequency;
Line 121:
Line 122: TryUpdateModel(paymentFrequency);
Line 123:
Line 124: if (!ModelState.IsValid)
It sounds like the metadata class you have attached to your PaymentFrequency model may have properties the model itself doesn't.

Resources