Termatrac - Recent changes [en]

Internal Glossary

Wikiadmin — Fri, 29 May 2026 04:05:50 GMT

Created page with "Under construction..."

New page

Under construction...

Dev:Webhooks

Wikiadmin — Wed, 27 May 2026 23:07:17 GMT

Email Problems and Resolutions

Wikiadmin — Wed, 27 May 2026 00:44:45 GMT

Created page with "From time to time, Email messages of Focused, Other"

New page

From time to time, Email messages of

Focused, Other

Support

Wikiadmin — Wed, 27 May 2026 00:43:43 GMT

← Older revision		Revision as of 02:43, 27 May 2026
Line 8:		Line 8:
	* [[Internal Glossary]]		* [[Internal Glossary]]
	* [[Support for Android and iOS Devices]]		* [[Support for Android and iOS Devices]]
			* [[Email Problems and Resolutions]]

User:Zg

Wikiadmin — Tue, 26 May 2026 02:21:54 GMT

User account Zg was created by Wikiadmin and password was sent by email

User:Cristine

Wikiadmin — Tue, 26 May 2026 02:21:03 GMT

User account Cristine was created by Wikiadmin and password was sent by email

IT:Company Customer Provision

Wikiadmin — Tue, 26 May 2026 02:11:56 GMT

So many Email addresses

Wikiadmin — Fri, 22 May 2026 06:25:45 GMT

Created page with "(mostly answered by Claude.AI) At the UI level, there is '''no direct Email ID field on the Customer DocType itself'''. It '''is''' redundant by design, and it's a known architectural quirk in ERPNext. Here's why both exist and what each one actually does: ---- == The Two Fields Explained == === 1. <code>Contact.is_primary_contact</code> (on the Contact DocType) === * This is a '''flag on the Contact record itself''' * It means: ''"among all contacts linked to this..."

New page

(mostly answered by Claude.AI)

At the UI level, there is '''no direct Email ID field on the Customer DocType itself'''.

It '''is''' redundant by design, and it's a known architectural quirk in ERPNext. Here's why both exist and what each one actually does:
----

== The Two Fields Explained ==

=== 1. <code>Contact.is_primary_contact</code> (on the Contact DocType) ===

* This is a '''flag on the Contact record itself'''
* It means: ''"among all contacts linked to this customer, this one is the primary"''
* It is set when you tick '''"Is Primary Contact"''' on the Contact form
* ERPNext uses this to '''auto-populate''' contact fields in transactions (Sales Order, Sales Invoice, etc.)
* '''Problem:''' Nothing enforces uniqueness — two contacts for the same customer can both have <code>is_primary_contact = 1</code>, which is a data integrity gap

----

=== 2. <code>Customer.customer_primary_contact</code> (on the Customer DocType) ===

* This is a '''direct link field''' (a <code>Link</code> field pointing to <code>Contact</code>) stored on the Customer record itself
* It gives you a '''single, authoritative lookup''': ''"what is the primary contact for this customer?"'' without having to query the Contact table at all
* It is updated automatically by ERPNext when a contact is marked as primary
* Much faster for API queries — one GET on the Customer record returns the primary contact name immediately

----

== Why Both Exist — The Real Reason ==
<code>Customer ──────────────────────────────────────────────────────────┐
customer_primary_contact = "Jane Smith" ← fast denormalised │
lookup │
│
Contact (Jane Smith) │
links → [{ link_doctype: "Customer", link_name: "CUST-00001" }] │
is_primary_contact = 1 ← flag used during transaction │
auto-population & filtering ───────────┘</code>
It is essentially '''denormalisation for performance''' — a classic database trade-off:
{| class="wikitable"
!Concern
!<code>is_primary_contact</code>
!<code>customer_primary_contact</code>
|-
|'''Where stored'''
|Contact record
|Customer record
|-
|'''Purpose'''
|Flag for filtering/transactions
|Fast direct lookup
|-
|'''Query cost'''
|Requires JOIN / filter on Contact
|Single field on Customer fetch
|-
|'''Risk'''
|Multiple contacts can be flagged <code>1</code>
|Can go stale if not synced
|-
|'''Updated by'''
|User manually / Contact save hook
|ERPNext hook on Contact save
|}
----

== The Sync Risk ==
The real danger is they can '''fall out of sync''':

* If you update <code>is_primary_contact</code> via a direct API PATCH on the Contact but ERPNext's server-side hook doesn't fire correctly, <code>customer_primary_contact</code> on the Customer won't update
* If you delete a Contact that is the primary, <code>customer_primary_contact</code> may hold a '''dead reference''' until another contact is promoted

----

== Practical Advice ==
{| class="wikitable"
!Use case
!Use this field
|-
|Fetch primary contact quickly in one API call
|<code>Customer.customer_primary_contact</code>
|-
|Filter all contacts to find which is primary
|<code>Contact.is_primary_contact = 1</code>
|-
|Trust for data integrity
|Neither alone — '''verify both match'''
|-
|Setting a new primary contact
|Always do it via the '''ERPNext UI or server-side method''' so both fields stay in sync
|}
---- It's a deliberate denormalisation that trades data integrity risk for query performance, and it's something ERPNext developers themselves have debated in the Frappe GitHub issues over the years.

ERPNext's <code>Address</code> DocType also has its own <code>email_id</code> field, completely separate from the Contact email chain.
----

== The Full Picture ==
<code>Customer (CUST-00001 - "Acme Corp")
│
├──► customer_primary_contact ──► Contact "Jane Smith"
│ │ └── email_ids[]
│ │ └── jane@acme.com ← person email
│
├──► customer_primary_address ──► Address "Acme Corp-Billing"
│ └── email_id: accounts@acme.com ← address email
│
└──► Dynamic Links (multiple)
│
├── Address "Acme Corp-Billing"
│ └── email_id: accounts@acme.com
│
├── Address "Acme Corp-Shipping"
│ └── email_id: warehouse@acme.com
│
└── Address "Acme Corp-Head Office"
└── email_id: info@acme.com</code>
----

== Three Completely Separate Email Pools ==
{| class="wikitable"
!Source
!Field
!Typical Use
!Example
|-
|<code>Contact.email_ids[]</code>
|<code>email_id</code>
|Person-to-person communication
|<code>jane@acme.com</code>
|-
|<code>Address.email_id</code>
|<code>email_id</code>
|Location/department email
|<code>accounts@acme.com</code>
|-
|<code>Customer</code>
|''(none)''
|—
|—
|}
Each pool is '''entirely independent''' — no sync, no relationship between them whatsoever.
----

== Why Address Has Its Own Email ==
The <code>Address</code> DocType is designed to represent a '''physical or operational location''', and in B2B that location often has its own functional email:
<code>Acme Corp - Billing Address → accounts@acme.com (AP/AR team)
Acme Corp - Shipping Address → warehouse@acme.com (logistics team)
Acme Corp - Head Office → info@acme.com (general enquiries)</code>
This makes sense in the real world — when you send an '''invoice''', you email the billing address email, not Jane's personal email.
----

== How ERPNext Decides Which Email to Use ==
This is where it gets messy. Depending on the transaction type, ERPNext picks email from '''different sources''':
{| class="wikitable"
!Transaction
!Where ERPNext looks for email
|-
|Sales Invoice (send via email)
|<code>customer_primary_contact → email_id</code>
|-
|Print & Email from Address
|<code>Address.email_id</code>
|-
|Dunning / Payment Reminder
|<code>customer_primary_contact → email_id</code>
|-
|Shipping Notification
|<code>Address.email_id</code> (shipping address)
|-
|Portal / User login
|<code>Contact.email_ids[]</code>
|}
There is '''no single unified "customer email"''' — it depends entirely on the context and which button you press.
----

----

== Summary of the Design Problem ==
{| class="wikitable"
!Issue
!Impact
|-
|No single <code>Customer.email</code> field
|Must chase 2+ DocTypes to find any email
|-
|Address email ≠ Contact email
|Easy to send invoices to the wrong place
|-
|No enforced "use this email for invoices" rule
|Relies on user discipline
|-
|Multiple addresses, each with own email
|No clear hierarchy without <code>is_primary_address</code> logic
|-
|ERPNext picks email source based on transaction
|Inconsistent and surprising behaviour
|}
It is a '''flexible but fragile''' design — powerful when set up correctly, but very easy to end up with missing or stale email data across the system.

IT:Company Customer Provision

Wikiadmin — Fri, 22 May 2026 06:15:50 GMT

File:Imagesdfsd3432.png

Wikiadmin — Fri, 22 May 2026 05:30:45 GMT

Wikiadmin uploaded File:Imagesdfsd3432.png

New page

867686786767

IT:Company Customer Provision

Wikiadmin — Tue, 19 May 2026 03:49:59 GMT

Auto Provision

File:Image889klasjdkjdsw.png

Wikiadmin — Tue, 19 May 2026 03:45:37 GMT

Wikiadmin uploaded File:Image889klasjdkjdsw.png

New page

8skkwesdafasdf

File:Imagekkl.png

Wikiadmin — Tue, 19 May 2026 03:40:42 GMT

Wikiadmin uploaded File:Imagekkl.png

New page

89klajsdf2

File:Imagesdf.png

Wikiadmin — Tue, 19 May 2026 03:39:04 GMT

Wikiadmin uploaded File:Imagesdf.png

New page

klklsadfkjdsffd

IT:Company Customer Provision

Wikiadmin — Tue, 19 May 2026 03:37:05 GMT

Created page with "Provision is to enable customers with at least 1 iTraker unit to be able to sign-in TT Customer Portal. And the end product of provision is: # A dedicated URL for the customer like: https://YourSubdoman.termatraconline.net/ # Username: YourSubdomain; Password: InitialPasswordYouShouldChangeRightAway. === Data Prerequisites === # Company customer in ErpNext. And the customer should be associated with at least 1 contact. # Counterpart company in ttonline, along with T5..."

File:Imagedffdgsd7878.png

Wikiadmin — Tue, 19 May 2026 03:23:50 GMT

Wikiadmin uploaded File:Imagedffdgsd7878.png

New page

dfgsdg

File:Imagesdfsdkiu7.png

Wikiadmin — Tue, 19 May 2026 03:18:54 GMT

Wikiadmin uploaded File:Imagesdfsdkiu7.png

New page

sadfsadd sdfasdfasdjklkjlkj

File:Imageffgd.png

Wikiadmin — Tue, 19 May 2026 03:08:46 GMT

Wikiadmin uploaded File:Imageffgd.png

New page

hjkjhhj

File:Imagesdfsdfsdfsdf.png

Wikiadmin — Tue, 19 May 2026 03:06:44 GMT

Wikiadmin uploaded File:Imagesdfsdfsdfsdf.png

New page

sdfsadfsadfsdfssdfdssd

File:Imageasdfsd.png

Wikiadmin — Tue, 19 May 2026 02:56:05 GMT

Wikiadmin uploaded File:Imageasdfsd.png

New page

asdfsdf

File:Imageddsafjsdf.png

Wikiadmin — Tue, 19 May 2026 02:50:28 GMT

Wikiadmin uploaded File:Imageddsafjsdf.png

New page

sdafsdfsdaf

IT:IT

Wikiadmin — Tue, 19 May 2026 02:44:38 GMT

Customer Portal

Wikiadmin — Mon, 18 May 2026 06:01:08 GMT

← Older revision		Revision as of 08:01, 18 May 2026
Line 1:		Line 1:
			== Features Highlight ==
			Termatrac Customer Portal offers the following major features:

			# View scans of a job, uploaded from the iTraker app.
			# [[Customer Portal Reporting\|Create report]] based on a job uploaded.
			# Review iTraker units associated with the customer.

	[[~~Customer Portal Reporting~~]]		== Prerequisites ==
	[[File:Portal.png\|thumb\|Termatrac Customer Portal]]		Each customer who has purchased at least1 iTraker unit should have an account in the customer portal, consist of the following:

			# A dedicated URL like [https://YourSubdomain.termatrac.net https://YourSubdomain.termatraconline.net].
			# Username as YourSubdomain.
			# Password.

			If you haven't got one during purchase, you may contact our support guys to do the provision for you.

			== Quick Start ==

			=== Portal Localized ===
			In the landing page [https://YourSubdomain.termatrac.net https://YourSubdomain.termatraconline.net], select your preferred language from .

			If you choose English, your customer portal URL will be: https://YourSubdomain.termatraconline.net/en/
			[[File:Imagelocalized.png\|center\|thumb\|localized]]

			=== Sign-in ===
			Input your username and password.

			'''Hints:'''

			* By default the username is the same as the subdomain name.

			[[File:Imagesigin.png\|center\|thumb\|Signin]]

			=== Homepage ===
			The homepage shows recent uploaded scans, up to 20.[[File:Portal.png\|thumb\|Termatrac Customer Portal\|center]]

			=== Jobs ===
			The table provides overview of all the uploaded jobs along with scans. And you can create a report from a job.
			[[File:Imagesdfsd.png\|center\|thumb\|jobs]]
			[[File:Imagesdfds.png\|center\|thumb\|scans of job]]

			=== Reports ===

			==== Overview ====
			[[File:Imagesdfuy.png\|center\|thumb\|reports overview]]

			==== Add or Edit Report ====
			[[File:Imagesddsf.png\|center\|thumb\|add or edit]]

			==== Report Preview ====
			[[File:Imagesdfsdf.png\|center\|thumb\|report preview]]

File:Imagesdfuy.png

Wikiadmin — Mon, 18 May 2026 05:59:15 GMT

Wikiadmin uploaded File:Imagesdfuy.png

New page

asdfdsaf

File:Imagesddsf.png

Wikiadmin — Mon, 18 May 2026 05:57:00 GMT

Wikiadmin uploaded File:Imagesddsf.png

New page

sdfdsf

File:Imagesdfsdf.png

Wikiadmin — Mon, 18 May 2026 05:54:33 GMT

Wikiadmin uploaded File:Imagesdfsdf.png

New page

sdfsdfs

File:Imagesdfds.png

Wikiadmin — Mon, 18 May 2026 05:49:09 GMT

Wikiadmin uploaded File:Imagesdfds.png

New page

sdfsdfs

File:Imagesdfsd.png

Wikiadmin — Mon, 18 May 2026 05:47:13 GMT

Wikiadmin uploaded File:Imagesdfsd.png

New page

sdfsdf

File:Imagesigin.png

Wikiadmin — Mon, 18 May 2026 05:37:24 GMT

Wikiadmin uploaded File:Imagesigin.png

New page

sdf sdfsad

File:Imagelocalized.png

Wikiadmin — Mon, 18 May 2026 05:34:06 GMT

Wikiadmin uploaded File:Imagelocalized.png

New page

localized

Online to Portal

Wikiadmin — Mon, 18 May 2026 05:07:23 GMT

← Older revision		Revision as of 07:07, 18 May 2026
Line 13:		Line 13:
	# Modern user interfaces friendly to Windows, MacOS and tablets running Android or iOS.		# Modern user interfaces friendly to Windows, MacOS and tablets running Android or iOS.
	# More secured.		# More secured.
	# The radar scan image is more similar to the trend line of stock market index.		# The radar scan image is more similar to the trend line of stock market index, and may scale matching the browser's window size.
	# Better support for multilingual reports.		# Better support for multilingual reports.

Statistics of Legacy before Migrating to ERPNext

Wikiadmin — Mon, 18 May 2026 05:00:09 GMT

Wikiadmin deleted page Statistics of Legacy before Migrating to ERPNext content was: "As documented in https://termatrac.atlassian.net/browse/KAN-399 As of 2025-10-09 == CRM == # TTOnline DB: T5owner 484; '''company: 4185, active 3732''' # Service Centre, JIP200 TermatracAust DB: table contacts: 2538; table dr_contacts: 2491, table dr_accs is '''company: 4160, active 3703''' associated with TTOnline via ExtId. # vTiger CRM: '''account (organization): 5...", and the only contributor was "Wikiadmin" (talk)

Dev:Webhooks

Wikiadmin — Mon, 18 May 2026 04:58:03 GMT

TagCustomerWithT5Owner (Tag a customer with T5Owner)

IT:ERPNext Exceptional Operations

Wikiadmin — Fri, 15 May 2026 03:33:33 GMT

Step 1: Move back to warehouse through Stock Reconciliation

Parking Newly Manufactured T5 with Termatrac Stock XXX

Wikiadmin — Fri, 15 May 2026 03:22:34 GMT

← Older revision		Revision as of 05:22, 15 May 2026
Line 1:		Line 1:
			This section is about initial setup for automatic parking newly manufactured T5 units at T5Owner "Termatrac Stock XXX".

	Initially we have warehouses with IDs "<code>Australia Warehouse - TT</code>" and "<code>USA Warehouse - TT</code>" to associate with ttonline T5Owner "Termatrac Stock" and "Termatrac Stock - USA", which are linked to respective calibration centers, essentially to calibration centers using the T5 calibration app.		Initially we have warehouses with IDs "<code>Australia Warehouse - TT</code>" and "<code>USA Warehouse - TT</code>" to associate with ttonline T5Owner "Termatrac Stock" and "Termatrac Stock - USA", which are linked to respective calibration centers, essentially to calibration centers using the T5 calibration app.

Parking Newly Manufactured T5 with Termatrac Stock XXX

Wikiadmin — Fri, 15 May 2026 03:20:08 GMT

Created page with "Initially we have warehouses with IDs "<code>Australia Warehouse - TT</code>" and "<code>USA Warehouse - TT</code>" to associate with ttonline T5Owner "Termatrac Stock" and "Termatrac Stock - USA", which are linked to respective calibration centers, essentially to calibration centers using the T5 calibration app. '''Remarks:''' * Noted that IDs has double-spaces: this may be due to typo during the creation of warehouses in ErpNext, and once the ID is created, it c..."

New page

Initially we have warehouses with IDs "<code>Australia Warehouse - TT</code>" and "<code>USA Warehouse - TT</code>" to associate with ttonline T5Owner "Termatrac Stock" and "Termatrac Stock - USA", which are linked to respective calibration centers, essentially to calibration centers using the T5 calibration app.

'''Remarks:'''

* Noted that IDs has double-spaces: this may be due to typo during the creation of warehouses in ErpNext, and once the ID is created, it cannot not be changed. Generally you should avoid double spaces, since visually it is hard to distinguish with single space, and the misreading may cause desired and easily overlooked mismatches. For examples, the names have no double spaces.

To expand the mapping:

# Create a new warehouse "NewRegion Warehouse".
# Create new customer "Termatrac Stock - NewRegion" to trigger the creation company record "Termatrac Stock - NewRegion" in ttonline.
# Tag it with "T5Owner" to trigger the creation of T5Owner record "Termatrac Stock - NewRegion" in ttonline, which will be associated with the newly created company.
# In TTONLINE Admin Portal, edit t5owner record: "Termatrac Stock - NewRegion". You will see a special text box "ErpNext Warehouse Id for stock transit".
## Copy&paste the ErpNext warehouse Id.
## Make sure the T5 owner is associated with the correct Cal. Centre.
## Save owner.

Then in next batches of manufacturing T5 units for the targeted warehouse, the newly created T5 units in ttonline will be associated with owner "Termatrac Stock - NewRegion", eventually associated with the correct cal. centre.

Dev:Webhooks

Wikiadmin — Fri, 15 May 2026 03:04:09 GMT

Create Sales Return based on a Delivery Note

Tips of the Week

Wikiadmin — Fri, 01 May 2026 04:03:16 GMT

← Older revision		Revision as of 06:03, 1 May 2026
(One intermediate revision by the same user not shown)
Line 31:		Line 31:

	* Some of the operations may result in sending notification Emails to customers. Generally you should avoid submitting respecting documents, otherwise the customer may get confused. If you really want to test, create a test customer with an Email address under your control.		* Some of the operations may result in sending notification Emails to customers. Generally you should avoid submitting respecting documents, otherwise the customer may get confused. If you really want to test, create a test customer with an Email address under your control.

			== List customers ==

			=== List customers in a city or state ===
			Document records in ErpNext are well normalized. One customer should have multiple addresses, and each address could be linked to other customers, banks and leads etc.

			==== Method 1: Using the Address List (Easiest) ====
			Since city and state are native fields in the Address doctype, the quickest way to see this data is via the Address list.

			# Go to '''Address List''' (search for "Address List" in the Awesome bar).
			# Click the '''Filter''' button at the top left.
			# Add a filter for '''City''' or '''State'''.
			# Then click the address and locate a row with Linked Document Type: "Customer", and hover over the Link Name cell, then click the "->" symbol.

			[[File:Image7887978.png\|center\|frame]]
			[[File:Image34534543.png\|center\|frame]]

			==== Method 2: Standard Reports ====
			ERPNext provides a standard report called the '''Address and Contact''', which is specifically designed for this purpose:

			# Search for '''Address and Contact''' in the search bar or just go https://erpstaging.termatrac.net/app/query-report/Address%20And%20Contacts
			# Use the filter bar at the top to filter by '''City''' or '''State'''.

			[[File:Image23432434234.png\|center\|frame]]
			'''Remarks:'''

			* Noted that for filtering by state, currently you have to go "City". And "Postal Code" is showing city, and "State" is showing zip code. Keep this in mind while this is likely a bug in ErpNext 15,

File:Image23432434234.png

Wikiadmin — Fri, 01 May 2026 03:55:03 GMT

Wikiadmin uploaded File:Image23432434234.png

New page

sdfsdf

File:Image34534543.png

Wikiadmin — Fri, 01 May 2026 03:43:58 GMT

Wikiadmin uploaded File:Image34534543.png

New page

sds

File:Image237867.png

Wikiadmin — Fri, 01 May 2026 03:41:31 GMT

Wikiadmin uploaded File:Image237867.png

New page

dfgfd

File:Image7887978.png

Wikiadmin — Fri, 01 May 2026 01:51:27 GMT

Wikiadmin uploaded File:Image7887978.png

New page

rte

Tips of the Week

Wikiadmin — Fri, 01 May 2026 01:02:20 GMT

← Older revision		Revision as of 03:02, 1 May 2026
Line 4:		Line 4:

	=== Distinguish between the production environment and the test environment ===		=== Distinguish between the production environment and the test environment ===
	We have a test environment for internal staffs to do self-training and build up confidence when finding a moment during busy daily operations.		We have a test environment for internal staffs to do self-training and build up confidence or muscle memory when finding a moment during busy daily operations.

	* https://erptest.termatrac.net/app ERPNext Test		* https://erptest.termatrac.net/app ERPNext Test
Line 21:		Line 21:
	And pick either Night or Light.		And pick either Night or Light.
	[[File:Image324234.png\|center\|thumb]]		[[File:Image324234.png\|center\|thumb]]

			==== Alter theme of TT Online Admin Portal ====
			Click the account profile button on the top right corner, and select "About".
			[[File:Image78978.png\|center\|thumb]]
			And select one of the themes.
			[[File:Image23434.png\|center\|thumb]]

			==== Warning ====

			* Some of the operations may result in sending notification Emails to customers. Generally you should avoid submitting respecting documents, otherwise the customer may get confused. If you really want to test, create a test customer with an Email address under your control.

File:Image23434.png

Wikiadmin — Fri, 01 May 2026 00:59:37 GMT

Wikiadmin uploaded File:Image23434.png

New page

3432

File:Image78978.png

Wikiadmin — Fri, 01 May 2026 00:56:55 GMT

Wikiadmin uploaded File:Image78978.png

New page

434

Tips of the Week

Wikiadmin — Fri, 01 May 2026 00:53:25 GMT

Created page with "These are tips mostly about user interaction to speed up operations and avoid confusion, not about the definition of business workflows. == User Interaction == === Distinguish between the production environment and the test environment === We have a test environment for internal staffs to do self-training and build up confidence when finding a moment during busy daily operations. * https://erptest.termatrac.net/app ERPNext Test * https://admintest.termatrac.net/en/ TT..."

New page

These are tips mostly about user interaction to speed up operations and avoid confusion, not about the definition of business workflows.

== User Interaction ==

=== Distinguish between the production environment and the test environment ===
We have a test environment for internal staffs to do self-training and build up confidence when finding a moment during busy daily operations.

* https://erptest.termatrac.net/app ERPNext Test
* https://admintest.termatrac.net/en/ TT Online Admin Portal Test

The login credential is the same as the production environment.

'''Tips:'''

# Use a Web browser different from the primary one you use for production. For example, if you are using Chrome for production, then use Edge for test. Vice versa.
# Use different theme of the Erpnext and TT Online Admin Portal. If you do so, probably you don't need tip 1.

==== Alter theme of ErpNext ====
Click the account profile button on the top right corner.
[[File:Imagesss.png|center|thumb]]
And pick either Night or Light.
[[File:Image324234.png|center|thumb]]