fix table mapping for events when cloning and creating new versions (#10444)

* fix table mapping for events when cloning and creating new versions

* add set-table-page mappping on duplicate page as well
This commit is contained in:
Kartik Gupta 2024-07-31 15:24:52 +05:30 committed by GitHub
parent 915b91297c
commit f405d3db74
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 11 additions and 0 deletions

View file

@ -1788,6 +1788,10 @@ export class AppImportExportService {
eventDefinition.modal = oldComponentToNewComponentMapping[eventDefinition.modal];
}
if (eventDefinition?.actionId == 'set-table-page' && oldComponentToNewComponentMapping[eventDefinition.table]) {
eventDefinition.table = oldComponentToNewComponentMapping[eventDefinition.table];
}
event.event = eventDefinition;
await manager.save(event);

View file

@ -517,6 +517,9 @@ export class AppsService {
eventDefinition.modal = oldComponentToNewComponentMapping[eventDefinition.modal];
}
if (eventDefinition?.actionId === 'set-table-page') {
eventDefinition.table = oldComponentToNewComponentMapping[eventDefinition.table];
}
event.event = eventDefinition;
await manager.save(event);

View file

@ -129,6 +129,10 @@ export class PageService {
eventDefinition.modal = componentsIdMap[eventDefinition.modal];
}
if (eventDefinition?.actionId === 'set-table-page') {
eventDefinition.table = componentsIdMap[eventDefinition.table];
}
event.event = eventDefinition;
const clonedEvent = new EventHandler();