Partner form: NAV fill-in, duplicate check, persons

The NAV-based fill-in of the partner form, the duplicate check, the visibility of client-level fields, saving the partner's persons and the permission keys.

For a new partner the partner master form is filled from the NAV taxpayer query; for an existing partner it manages the links to the person master. Company data is written by the company model, the person–company link by the person model.

Data model

Table names carry the installation's own prefix in the database.

Table	Role	Owner
`company`	partner; `company_taxhu`, `company_taxgroup`, `company_group_id`, client-level columns	company model
`company_validation`	validity audit (`check_type = nav_taxpayer`)	company model
`nav`	NAV API data	company model
`person_company`	person ↔ company: `role`, signatory flag, `contact_phone_ref`, `contact_email_ref` (0 = default)	person model

NAV fill-in

Client side: digits only, the first 8; without 8 digits "Tax number is not valid".
Server (taxpayer right): 8 digits required. The code takes the NAV credentials from the NAV settings of a company with a fixed ID (10); without them an error message. An unknown tax number and an empty response give separate errors.
Fill-in: name, short name, full tax number, group VAT ID, organisation type, address cards, validity (hidden fields and badge).
Leaving the name field runs a duplicate check (edit right): the same 8-digit core number blocks ("Warning: Value is already in use!" on saving), the same name only warns.
For a new partner validity is not written to the database; for an existing company in scope validity and an audit row are recorded.

Saving

canSave (add new, edit existing); content scope for existing ones. Name required ("Warning: Partner name is required!"), tax number dedup on the 8-digit core number.
Persons (with the person edit right): add link (only adds, never removes), position, the company's whole signatory set in one step, per-partner contacts. The person row arrives from the server as a complete row (with company list, person list and edit).
Client-level fields show only with a chosen company group, but are submitted even when hidden.

Permissions

Function rights: list, add, edit, delete, status, taxpayer (NAV query, validation, new partner from NAV), navapi (NAV API key block), revalidate, debug; the persons block needs list and edit on the person master.
Content scope: saving an existing company, the persons tile and writing NAV validity stay within scope.

Known limitations

The NAV credentials come hard-coded from the settings of a single company.
The help text of the signatory switch says one signatory per company, but the code allows several.

Related topics: NAV query tax number persons permissions

Request consultation Back to home