-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
INSERT statement conflicted with the FOREIGN KEY constraint for Payment methods and Regions #7
Comments
Hi @BenWhite27 Had a look at this on my project and I was able to reproduce the issue by doing the following steps which you provided:
Additionally, when deleting the region, if you have not cleared the dependency from the Payment method as a allow country or shipping method allow region/country that reference will stay in the database and not be cleared out. |
Quick update: In my case it was the Payment Method Allowed Regions table which still had references to some regions that were deleted. The instructions for Support were as follows, repeated for each payment method:-
This effectively rebuilds the relationships and clears the table of records related to the deleted regions. I still believe there is a bug or two present here.
|
Hey @BenWhite27 Really glad the workaround worked, and rest assured we will address this. We just wanted to ensure you weren't having to wait around for a fix to be released in the meantime. Thank you for raising this issue 🙌 |
Umbraco: v13.0.3
Deploy: v13.0.3
Commerce.Deploy: v13
TL;DR;
Deleted regions are not exported to UDAs but are still listed as dependencies in payment method UDAs
Full Info
When cloning my Cloud environment to my local PC the installer fails to deploy the schema to the fresh database. This is before the Restoring content phase happens. The same thing also happens when creating a new development environment in Umbraco Cloud.
The deploy.log output is at the bottom. Looking at the UDA files I can see that the problem artifact
umb://umbraco-commerce-payment-method/93b59042f0554000a0a2018c8757acd5
has umbraco-commerce-region dependencies listed that don't exist in the freshly created local database and aren't listed in the Live environment's backoffice either.In total the artifact has 10 region dependencies, which matches the live database, however 2 of them have deletedTimestamp values. Only 8 region UDA files are exported to disk, even after a fresh export to UDA performed in the live environment. I can also confirm that the
PaymentMethodAllowedCountryRegions
table has entries for the deleted regions too.I've had a support case with Umbraco Cloud since the beginning of January, but it's starting to feel like a bug to me so I thought I'd post here as well.
Can I safely remove the extra dependencies from the UDA file, or will they be added again with a fresh export?
The text was updated successfully, but these errors were encountered: