Closed tiagonmas closed 1 year ago
I already push some code to try to mitigate this.
when /where did you push the code to ? I checked master and dev and last updates where from 2 days ago before this happened ?
My last try didn't work. I just this commit to try to solve the issue.
I don't know why still complaints that DonorAddress is null when I'm not inserting anything new in the database. Anyway this is an small change.
Changed the way we are getting those entities when creating the notification. Now instead of getting these values from the database I force to get a WebUser and BasePayment that already exits. Hope this helps solve this issue that still showing in Applicaiton Insights.
I dont see any more issues in the last 24h. I think we can close this one. Closing ...
Describe the bug "An error occurred while saving the entity changes. See the inner exception for details. Cannot insert the value NULL into column 'Address1', table 'alimentestaideia.core.dbo.DonorAddresses'; column does not allow nulls. INSERT fails. "
BancoAlimentar.AlimentaEstaIdeia.Repository.PaymentNotificationRepository.AddEmailNotification
As seen in AppInsights