bcgov / bcgov/entity

COLIN API Sync Test

Open
#13,284 0 comments 0 reactions 0 assignees View on GitHub
ENTITY - DO NOT USE
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

**Describe the bug in current situation**
The length of the field in postgres is longer than the field in CPRD so when we try to send these filings back to CPRD it fails in the COLIN API.

**Previous Steps**
- Limit all parties(first name) on the UI to 20 chars
- Update the party schema first name to 20 chars
- Update legal api to use updated schema
Linked Ticket: #13058 [COLIN API failure - Front and Backend Change validation of the first name field in Coop IA UI and/or Corp Party table](https://app.zenhub.com/workspaces/entities-team-space-6143567664fb320019b81f39/issues/bcgov/entity/13058)

**Current Issue**
COLIN database is not syncing

**To Do List:**
- [ ] Test and make sure that COLIN is synced/pushed properly

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the linked ticket #13058 and tracing the COLIN sync path across the COLIN API, PostgreSQL party schema, legal API, and UI validation described here. Run the existing sync or push checks, if available, and confirm that the affected filings are successfully synchronized back to CPRD.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgres
Domain
api, backend, databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.