mirror of
https://github.com/renee-png/acmcc.git
synced 2026-06-21 01:40:01 +00:00
admin
6634907799
Each association now owns an independent set of chart_of_accounts rows. Two associations can both have a "5000" meaning different things, edited independently — previously buildium rows were shared across associations via the association_ids[] array, so editing one association's number edited it for all. - Data migration: split each shared buildium row into one row per association in its association_ids (excluding nulls and ids of deleted associations). The original row stays as the per-association row for its own association_id; clones are added for the others — nothing is deleted, so no FK dangles. 94 -> 370 buildium rows. References repointed by each record's association (bills, budgets, owner_ledger_entries, vendor_coa_mappings, units, vendors, journal_entries; budget_actuals_monthly is a view). parent_account_id remapped same-association; orphan-parent children become top-level. Pristine backup in public._coa_perassoc_backup. Ran in one transaction with in-line verification. - Uniqueness: drop (account_number, accounting_system); add UNIQUE(association_id, account_number) WHERE accounting_system <> 'platform' (platform rows mirror accounting.accounts and carry blank/dup codes). This also finally backs the buildium importers' existing onConflict target. - Keep association_ids as a single-element mirror of association_id during the transition so the admin COA page and direct array-contains callers keep working. - App: fetchChartOfAccounts scopes buildium/zoho by association_id when an association is given (was system-wide). Importers and sync_account_to_public_coa were already per-association; no change needed. Verified on live data: 370 singleton-array rows across 12 associations, zero intra-association duplicates, zero cross-association references or parents, and a live two-association "5000" independence test (create/rename/isolate) passed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Welcome to your Lovable project
Project info
URL: https://lovable.dev/projects/REPLACE_WITH_PROJECT_ID
How can I edit this code?
There are several ways of editing your application.
Use Lovable
Simply visit the Lovable Project and start prompting.
Changes made via Lovable will be committed automatically to this repo.
Use your preferred IDE
If you want to work locally using your own IDE, you can clone this repo and push changes. Pushed changes will also be reflected in Lovable.
The only requirement is having Node.js & npm installed - install with nvm
Follow these steps:
# Step 1: Clone the repository using the project's Git URL.
git clone <YOUR_GIT_URL>
# Step 2: Navigate to the project directory.
cd <YOUR_PROJECT_NAME>
# Step 3: Install the necessary dependencies.
npm i
# Step 4: Start the development server with auto-reloading and an instant preview.
npm run dev
Edit a file directly in GitHub
- Navigate to the desired file(s).
- Click the "Edit" button (pencil icon) at the top right of the file view.
- Make your changes and commit the changes.
Use GitHub Codespaces
- Navigate to the main page of your repository.
- Click on the "Code" button (green button) near the top right.
- Select the "Codespaces" tab.
- Click on "New codespace" to launch a new Codespace environment.
- Edit files directly within the Codespace and commit and push your changes once you're done.
What technologies are used for this project?
This project is built with:
- Vite
- TypeScript
- React
- shadcn-ui
- Tailwind CSS
How can I deploy this project?
Simply open Lovable and click on Share -> Publish.
Can I connect a custom domain to my Lovable project?
Yes, you can!
To connect a domain, navigate to Project > Settings > Domains and click Connect Domain.
Read more here: Setting up a custom domain