- ABP Framework version: v3.3.2
- UI type: Angular
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): yes
- Exception message and stack trace:
- Steps to reproduce the issue:"
Hi, I am upgrading our ABP framework from version 3.3.2 to 4.4.4 and found that new tables related to payment were added after executed add-migration command, below are the table names:
PayPaymentRequests, PayPlans, PayPaymentRequestProducts, PayGatewayPlans
Are these tables related to payment module? why do we need them? our solution does not have dependencies on payment module.
1 Answer(s)
-
0
Hi @nhontran
In that version, Saas module is dependent on Payment module because of technical issues. That dependency is removed in v5,
You can remove those tables from migrations if you don't use it. https://support.abp.io/QA/Questions/2509/Remove-Pay-tables-from-Database-through-migrations#answer-81fc4c0a-24eb-af2a-b398-3a01c1e58c5b
But Make sure you haven't disabled the PayPlans table.
