A field shows a code instead of a name
Every value MarqIQ shows you is meant to be the label your tool shows, resolved once when the data is read — picklist options, owner names, campaign names, stage names, form names. A raw code on screen means one of a small number of things went wrong, and this article names each one and what clears it. If the column header rather than the value is the problem, read A field is missing from MarqIQ instead.
Before you start
Note down three things before you read on: which screen you are on, which tool the column came from, and the value itself. The shape of the value decides which of the causes below is yours.
What counts as a code
MarqIQ treats three shapes as an identifier rather than a value: a run of eight or more digits, a GUID in the 8-4-4-4-12 form, and a Salesforce id — 15 or 18 letters and digits with a three-character object prefix and at least one digit in it. “Enterprise Sales” is a value. “701WQ00001PiqiOYAR” is an id.
How a label is meant to reach your screen
A CRM stores the internal value on the record and keeps the human label somewhere else — in the property definition, in the owner record, in the campaign. MarqIQ resolves all of them once per tool and object, then applies the result to every row, so no screen has to know where a label came from.
| What is resolved | Where the label comes from | How long it is kept |
|---|---|---|
| Picklist and dropdown values | The field catalog the sync saves. Only HubSpot’s sync saves the options themselves, up to 500 per field | Rewritten on each sync |
| Picklist values on HubSpot when the catalog holds no options | HubSpot’s own property definitions, one call per object | 24 hours |
| Owner ids | HubSpot’s owners API. On every other tool the sync stores the name on the row as it writes it | 24 hours |
| Campaign ids | A connected Salesforce for 701… ids, HubSpot’s marketing campaigns API for GUIDs | 24 hours |
| HubSpot’s standard lifecycle values | A fixed list in MarqIQ — “customer” reads Customer | Always |
| Form ids | HubSpot’s form list, read one page at a time | 24 hours |
Every cache above lives in your workspace’s own database.
Note
A value made of several ids — HubSpot joins them with a semicolon — is resolved part by part. A part that cannot be named keeps its id rather than being dropped, so the value you see is never shorter than the value that is stored.
The causes, by what the value looks like
An owner column reads Owner #12345
Why: The id could not be turned into a name. MarqIQ prints it this way on purpose: a bare 12345 in a column of numbers would read as a count, and that is a worse mistake than an unresolved name.
Fix: On HubSpot, check the connection is still live — the owners list is fetched with your HubSpot credentials, and a disconnected tool has none. On every other tool the name is written onto the row by the sync, so run a sync and the rows written after it carry the name.
A stage, status or dropdown column reads a long number such as 3387351250
Why: That is a HubSpot custom picklist option, whose internal value is a number. It appears when the field catalog for that object holds no options for that field yet — usually because the last sync predates the catalog carrying them.
Fix: Run a sync for that tool. The sync rewrites the field catalog with each field’s options as it goes. On HubSpot, MarqIQ also falls back to asking HubSpot for the property definitions directly, so the value normally resolves on the next read even before the sync finishes.
A picklist column shows codes on Pipedrive, Salesforce, Zoho CRM, Microsoft Dynamics, Marketo or Marketing Cloud
Why: Their field catalogs do not carry the options. Pipedrive saves how many options a field has but not what they are; Salesforce, Marketo and Marketing Cloud save the field’s name and type only; Zoho CRM and Microsoft Dynamics save no field catalog at all. Picklist labels therefore resolve on HubSpot today and nowhere else.
Fix: Nothing on your side will clear this, and no sync will. Where the tool stores a readable value — most Salesforce picklists store their label as the value — you already see the words. Where it stores a code, name the field in a support case so the gap is recorded against that tool.
A campaign column reads 701WQ00001PiqiOYAR or a GUID
Why: HubSpot’s Salesforce sync writes Salesforce campaign ids onto contacts and deals, and a HubSpot marketing campaign is referenced by its GUID. The only system that knows the name is the one that owns the id.
Fix: Connect Salesforce to this workspace so MarqIQ can look the names up. It reads up to 500 distinct ids per screen, 200 to a query. Above that, the ids beyond the 500 keep their raw form.
A value that used to show a name now shows its code
Why: The option, owner or campaign was deleted in the tool. The record still holds the stored value, and there is no longer a label anywhere to resolve it to.
Fix: Nothing can recover it from the tool. Decide what the records should hold instead and correct them at the source; MarqIQ shows what is stored.
A report you built shows “customer” or “NEW” rather than Customer or New
Why: This is deliberate, and only in the report builder. Saved reports filter on the value your tool stores, so relabelling every readable value would break the filters people already saved. In the report builder MarqIQ relabels id-shaped values only and leaves readable internal values alone.
Fix: Rename the column in your report, or read the same figure on the Data Audit or Analysis tabs, where every value is relabelled.
A form column shows an id rather than a form name
Why: MarqIQ’s own capture stores the form’s id and nothing else. Names come from HubSpot’s form list; where the form is not a HubSpot form, or the list could not be read, there is no name to show.
Fix: Check the page the form sits on, which MarqIQ falls back to when it has no name. On HubSpot, confirm the connection is live and re-open the screen the next day, after the form list is fetched again.
Before a report goes to a client
Run a sync for the tool the report reads.
This rewrites the field catalog, which is where picklist labels come from.
Open the report and scan each column for the three id shapes.
Long numbers, GUIDs, and 15 or 18-character strings starting with a three-character prefix.
Connect Salesforce first if any campaign column carries 701… ids.
Without it those stay as ids however many times you refresh.
Replace any column you cannot resolve, rather than shipping it.
A client who sees one code stops trusting the columns that are correct.
Name the tool and the field in a support case for anything left.
A picklist that cannot resolve on a tool other than HubSpot is a gap in MarqIQ, not in your data.
Take care
Do not fix a code by typing the label into your own report by hand. The next sync brings the same code back, and the two versions then disagree with each other in a way nobody can trace.
If it did not work
You ran a sync and the code is still there
Why: Labels other than picklist options are cached for 24 hours, and a sync does not clear those caches.
Fix: Wait a day and re-open the screen, or check the cause table above — a value on a tool whose catalog carries no options will not resolve at all.
One screen shows the name and another shows the code for the same record
Why: The report builder relabels id-shaped values only, so that saved filters keep matching the values your tool stores. Every other screen relabels everything it can.
Fix: Read Two screens show different numbers for the same thing for the other pairs that differ by design.
Half the ids in one value resolved and half did not
Why: A value holding several ids is resolved part by part, and an unresolved part keeps its id so nothing is silently dropped.
Fix: Check whether the unnamed ids belong to a system you have not connected. Salesforce campaign ids need a Salesforce connection even when the record lives in HubSpot.
Next steps
Related articles
Was this article helpful?