Support both link columns and plain foreign key columns
All checks were successful
Deploy HiHala Dashboard / deploy (push) Successful in 6s
All checks were successful
Deploy HiHala Dashboard / deploy (push) Successful in 6s
Production NocoDB uses DistrictId/MuseumId columns instead of nc_epk____ link columns. Code now checks both column names. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -149,7 +149,8 @@ export interface NocoDBMuseum {
|
||||
Id: number;
|
||||
Code: string;
|
||||
Name: string;
|
||||
'nc_epk____Districts_id': number;
|
||||
DistrictId?: number;
|
||||
'nc_epk____Districts_id'?: number;
|
||||
}
|
||||
|
||||
export interface NocoDBDailyStat {
|
||||
@@ -159,7 +160,8 @@ export interface NocoDBDailyStat {
|
||||
Tickets: number;
|
||||
GrossRevenue: number;
|
||||
NetRevenue: number;
|
||||
'nc_epk____Museums_id': number;
|
||||
MuseumId?: number;
|
||||
'nc_epk____Museums_id'?: number;
|
||||
}
|
||||
|
||||
// Translation function type
|
||||
|
||||
Reference in New Issue
Block a user