Failed to pack from snapshot: Solution pack failed: The assembly compilation returned the following errors: * AddSeafarer.xaml: error BC30456: ‘ChangesSummary’ is not a member of ‘DatesRecordsAuditLog’.
This error keeps on existing even though we tried to remove the entity itself from the project, rebuild every activities that uses this entity, and even deleting the activities related to it and its entity. Yet this error still exist when we deploy.
Hi @Nahte_16 ,
This error usually means that some workflow, generated code, or cached metadata is still referencing the field/property ChangesSummary from the entity DatesRecordsAuditLog, even though the entity or column was removed.
Try these steps:
Search the entire project for ChangesSummary and DatesRecordsAuditLog.
Use Ctrl + Shift + F in Studio.
Check all XAML files, variables, expressions, and arguments.
Refresh Data Service Entities
Remove the entity reference.
Re-add/synchronize the Data Service entities.
Verify that ChangesSummary no longer exists in the entity definition.
Clear Cached Files
Close Studio.
Delete the project’s .local folder and bin/obj folders (if available).
Reopen and rebuild the project.
Check AddSeafarer.xaml and AddRepat.xaml
The error screenshot specifically points to these files.
This looks like a stale reference/cache issue. ChangesSummary is still being referenced by DatesRecordsAuditLog somewhere in the project, even though the entity/activity was removed.
Try closing Studio, delete the .local/project cache if applicable, reopen the project, then Clean → Rebuild → Publish.
Also search the entire project for ChangesSummary to find any remaining references in XAML files or expressions.
in Studio Web, you won’t find the .local or project cache folders like in Studio Desktop.
Instead, search the project/workflow for ChangesSummary and check for any remaining references to DatesRecordsAuditLog.
If there are no references, try creating a new version/copy of the workflow and publish it again. This can help if the issue is caused by stale project metadata.
@Nahte_16 In Studio Web Solutions, the entity schema snapshot is cached at the Solution level, not just inside individual workflows. Even after removing activities in AddSeafarer.xaml, the Solution packaging step still compiles against the Solution’s registered schema snapshot.
Go to the Solution dashboard, open the Data Service / Data Fabric resource tab, and click Update Configuration or Refresh Schema for DatesRecordsAuditLog. That forces the Solution to regenerate its compiled model without the old ChangesSummary field.
If the entity was already deleted from Data Service entirely, remove the entity resource directly from the Solution’s Resources list, unlink AddSeafarer from the Solution overview, save, and then link it back. That flushes the cached snapshot so publishing succeeds.
For Studio Web, there is no .local folder that you can delete manually. Instead, try reloading the project, removing and re-adding the entity, republishing the Data Service entity changes, and creating a new project version/snapshot. The error usually means a reference to ChangesSummary still exists somewhere in the workflows or entity mappings.
If publishing a solution is failing, I’d first check that all dependencies and project references are valid and that the package/project versions are compatible. Also try restoring the project dependencies and publishing again. If it still fails, the detailed Output/Logs message usually points to the specific dependency causing the issue.
