Why English? | Reading Excel Linked Data Types Before Refreshing Stocks or Geography

Excel linked data types matter because a familiar word can become a connected entity with fields, sources and values that change when refreshed. Reading the interface well helps students and adults distinguish typed text from a matched company, financial instrument, country, city or administrative area.

This guide explains why English matters when reading Excel linked data types before refreshing Stocks or Geography. It covers entity matching, question-mark selectors, data cards, extracted fields, formulas, refresh scope, compatibility, source language and responsible limits.

The practical value reaches school research, further study and work. Good English makes a spreadsheet auditable: readers can tell what was matched, which field was used, when the value changed and whether the sentence built from it stays within the evidence.

Reading routes

• Understand entities and availability: Chapters 1–4.
• Inspect cards, fields and formulas: Chapters 5–7.
• Control refresh scope and time: Chapters 8–10.
• Compare geography and preserve compatibility: Chapters 11–13.
• Transfer into school and work: Chapters 14–16.

Chapter 1 of 17: A linked data type is an entity connection, not decorated text

The mechanism

Excel can convert text such as a company, fund, country or city into a linked data type connected to an online source. The small icon indicates that the cell now represents an entity with fields, not merely the letters that were typed.

English matters because “Stocks”, “Geography”, “convert”, “linked” and “source” describe a change in what the cell means. Readers must distinguish the visible label from the entity Excel matched behind it.

A practical example

A cell contains “Singapore”. As plain text it is a word. As a Geography data type it can expose fields such as population or capital, depending on the source and available schema. The label looks similar, but the workbook now depends on an external connection.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

A linked entity is not automatically correct. Matching, source coverage, time and field definitions still require review.

• Check for the linked-data icon.
• Open the card to identify the entity.
• Record the source and relevant field.
• Keep the original input visible when ambiguity matters.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Next chapter

Chapter 2 of 17: Read account, edition and language requirements

The mechanism

Microsoft’s current support pages describe Stocks and Geography for Microsoft 365 or eligible Microsoft accounts, with platform and editing-language conditions. These boundaries can explain why one person sees the feature and another does not.

Terms such as “applies to”, “requires”, “available” and “editing language” are operational conditions. Skipping them turns a support page into an unrealistic promise.

A practical example

A group member using a different account cannot convert the cells and assumes the file is corrupt. A careful check compares edition, sign-in state, editing language and connection before changing the workbook.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

Managed school or workplace accounts can apply additional policies. Product support documentation cannot guarantee identical access on every device.

• Confirm the signed-in account.
• Check the Excel edition and platform.
• Verify an eligible editing language.
• Plan a text-only fallback for collaborators.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter · Next chapter

Chapter 3 of 17: Stocks means several financial instrument types

The mechanism

Microsoft’s linked-data gallery uses Stocks as a broad category that may include equities, funds, indexes, currency pairs, commodities and other instruments. The word “stock” in the button should not be read as one narrow security class.

Category reading prevents false assumptions. A label can name a family of entities, while the data card identifies the specific instrument, market and fields.

A practical example

A student types an organisation name and receives several possible listings. Choosing the first result may attach the wrong exchange or instrument. The selector and card must be read before extracting price or change.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

The feature does not provide investment advice, guarantee real-time accuracy or remove the need to understand market conventions and delays.

• Use a ticker, exchange or fuller name when needed.
• Confirm instrument type and market.
• Check the source note in the card.
• Do not describe a value as live unless the source says so.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter · Next chapter

Chapter 4 of 17: Geography names can point to different places

The mechanism

A city, district, province or country can share a name with another location. Linked data types therefore rely on entity resolution, and a question-mark icon can signal that Excel needs help selecting the intended match.

English contributes disambiguation. Adding a country, region or administrative level gives the name enough context for both people and software.

A practical example

The entry “Cambridge” could refer to places in the United Kingdom, the United States or elsewhere. A workbook for a school project should identify the country and administrative context before population fields are used.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

Administrative names and boundaries can change. A data card is evidence from a source at a time, not a permanent definition of place.

• Add country or region context.
• Use the selector when Excel shows uncertainty.
• Check the administrative level.
• Date claims that may change.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter · Next chapter

Chapter 5 of 17: The question-mark icon is a request for resolution

The mechanism

Microsoft explains that a question-mark icon appears when Excel has difficulty matching the text. It is not a decorative warning; it opens a selector where the reader can search and choose an entity.

A useful response begins by reading the uncertainty. Correcting spelling, adding context and comparing candidates are stronger moves than repeatedly refreshing an unresolved cell.

A practical example

A student sees a question mark beside a company name and immediately extracts a blank Price field. The better sequence is to resolve the entity first and only then add fields.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

The selector’s candidates come from the available source. If the intended entity is absent, forcing a near match can create convincing but wrong data.

• Correct obvious spelling errors.
• Add a discriminating keyword.
• Compare candidate descriptions.
• Leave the value as text when no match is reliable.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter · Next chapter

Chapter 6 of 17: The data card reveals fields and provenance

The mechanism

Selecting the icon opens a card with field-value pairs and a “Powered by” note. The card is the place to inspect what the entity contains, what fields are available and where the information comes from.

English reading moves from label to definition. A field named “Population”, “Price” or “Change” needs a unit, date, scope and source before it can support a claim.

A practical example

Two students copy a population number but disagree about the year. The card may expose the value without answering every methodological question. They should follow the source when the assignment requires a dated statistic.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

A source name does not mean every field has the same update schedule or methodology. Do not infer details that the card or provider does not state.

• Open the card before building formulas.
• Read field labels and units.
• Note the provider.
• Follow the original source for high-stakes claims.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter · Next chapter

Chapter 7 of 17: Insert Data turns entity fields into worksheet columns

The mechanism

Excel can extract fields from a linked entity using the Insert Data button. In a table, entering a field name in the header may populate a column. This is powerful because one entity column can support structured analysis.

Column headings are promises to readers. A clear heading identifies the field, unit, date or transformation so the numbers remain interpretable after the icon is out of view.

A practical example

A geography table adds “Area” and “Population” but then calculates density without checking whether area units align. The formula may run correctly while the claim is wrong.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

Automation propagates both good definitions and bad ones. Confirm one row and one formula before filling a large table.

• Use explicit field names.
• Include units in headings when practical.
• Check one extracted value against the card.
• Review calculated fields separately.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter · Next chapter

Chapter 8 of 17: Dot formulas make the field relationship visible

The mechanism

Microsoft documents formulas that reference a data type with a dot, allowing a cell such as A2 to expose a chosen field. Formula autocomplete can show available fields for that entity.

The dot behaves like a relationship phrase: take this entity’s named field. Understanding that grammar helps students read formulas rather than memorise punctuation.

A practical example

A formula requests a field that is unavailable for one entity and returns an error. The user should inspect the entity and field, not assume every row has identical coverage.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

Formula syntax cannot guarantee semantic comparability. Two entities may have values based on different dates or coverage rules.

• Read the formula aloud as entity plus field.
• Use autocomplete to avoid guessed field names.
• Check missing values before averaging.
• Document any exclusions.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter · Next chapter

Chapter 9 of 17: Refresh and Refresh All have different scope

The mechanism

Microsoft distinguishes refreshing a selected linked data type from Data > Refresh All, which can also update queries, connections and PivotTables in the workbook. The word “all” carries a wider operational scope.

Scope words are safety controls. Before refreshing, readers should know which values may change and which downstream tables, formulas or charts depend on them.

A practical example

A student intends to update one stock cell but chooses Refresh All in a workbook with several queries. Multiple results change just before submission. A controlled refresh would have been easier to audit.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

Refreshing replaces cached values with what the source currently returns. It is not an undoable truth update; it is a data operation that may change analysis.

• Choose selected refresh when testing.
• Save or version the workbook first.
• Review dependent charts and totals.
• Record the refresh date.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter · Next chapter

Chapter 10 of 17: Automatic refresh changes when evidence changes

The mechanism

Excel can support automatic refresh behaviour for linked data types in current versions. A workbook may therefore display different values at a later opening even when the formulas are unchanged.

Time language becomes essential. “As at”, “retrieved on”, “previous close”, “current” and “last updated” prevent a changing value from being mistaken for a timeless fact.

A practical example

Two screenshots of the same workbook show different market values. Neither necessarily proves an error; they may represent different refresh times. The report should state which snapshot supports the analysis.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

Automatic refresh can fail because of account, connection, source or compatibility issues. A timestamp and saved evidence remain useful.

• Know whether automatic refresh is enabled.
• Capture the relevant date and time.
• Keep a stable snapshot for assessed work.
• Explain later differences rather than hiding them.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter · Next chapter

Chapter 11 of 17: Financial data needs disciplined uncertainty language

The mechanism

Stock fields can be useful for learning about data, but prices, changes and company information can be delayed, revised or market-specific. A classroom spreadsheet should distinguish observation from recommendation.

Words such as “shows”, “suggests”, “during”, “based on” and “does not prove” help students make bounded claims. English prevents a single value from becoming an exaggerated forecast.

A practical example

A student writes that a rising price means a company “will succeed”. The data only shows a movement for a period and source. A better sentence identifies the interval and avoids predicting an outcome.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

Do not use a classroom linked-data exercise as personal financial advice. High-stakes decisions require appropriate professional and primary market information.

• State the period observed.
• Separate price movement from business quality.
• Avoid guaranteed future language.
• Cite official filings for company claims.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter · Next chapter

Chapter 12 of 17: Geographic data needs scale and boundary awareness

The mechanism

Geography fields may refer to countries, cities or administrative divisions. Comparisons only make sense when the entities use compatible scales and field definitions.

English helps name the unit of comparison. “City proper”, “urban area”, “municipality” and “metropolitan region” are not interchangeable, even when casual speech uses one place name.

A practical example

A class ranks cities by population using mixed entity types. The chart looks precise but compares unlike boundaries. The repair is to identify each administrative level and use a consistent source definition.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

Linked fields are a starting point for inquiry, not a substitute for geographic methodology or official statistics.

• Check entity type and boundary.
• Use like-for-like comparisons.
• Follow official statistical definitions.
• Explain exclusions and uncertainty.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter · Next chapter

Chapter 13 of 17: Compatibility warnings protect collaborators

The mechanism

Older Excel versions may not support linked data types and can display compatibility warnings or converted values differently. A workbook designed on a current subscription may not remain fully interactive elsewhere.

Compatibility language explains what will be preserved, converted or lost. Readers should not click through a warning before identifying the consequence for formulas and refresh.

A practical example

A student sends the workbook to a teammate using an older version. The visible values remain, but the linked cards and refresh workflow do not. A shared PDF or values-only sheet may be needed for review.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

Flattening to values improves portability but removes the live connection and some provenance. Keep an original workbook when the link matters.

• Ask which Excel version collaborators use.
• Read compatibility messages.
• Separate a live master from a portable copy.
• Label snapshots as non-refreshing.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter · Next chapter

Chapter 14 of 17: Errors should be described before they are fixed

The mechanism

Refresh errors, missing fields, blocked data types and unresolved entities have different causes. “Excel is wrong” provides too little information for a useful response.

Diagnostic English identifies the cell, entity, icon, field, error text, account and last successful step. That description supports a bounded test instead of random changes.

A practical example

A Geography cell refreshed yesterday but now shows an error on one device. Comparing the same workbook on the web and desktop versions can reveal whether the issue is local, account-based or source-related.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

Do not replace a missing value with a guessed number merely to complete a chart. Missingness is information and should be reported.

• Copy the exact error text.
• Inspect the entity card.
• Check account and connectivity.
• Use NA with an explanation when evidence is unavailable.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter · Next chapter

Chapter 15 of 17: A school geography project can teach source-aware data literacy

The mechanism

Linked Geography data types can help students build tables, maps or comparisons quickly. The educational value comes from asking what each field means, where it came from and whether entities are comparable.

MOE’s digital-literacy framing emphasises finding, thinking, applying and creating. English connects those steps by making search terms, definitions, interpretations and limitations explicit.

A practical example

A project compares three countries using population, area and capital. Students first resolve the correct entities, then verify units, calculate density and explain why one number cannot describe quality of life.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

A convenient data card should not replace official national statistics when the assignment requires authoritative current figures.

• Write a research question before collecting fields.
• Create a data dictionary.
• Verify one value per field against an official source.
• Explain what the table cannot answer.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter · Next chapter

Chapter 16 of 17: Career and workplace use requires an audit trail

The mechanism

Analysts, administrators and communicators often refresh data that feeds dashboards or briefings. The workbook should reveal who refreshed it, when, from which source and what changed.

English creates the audit trail through filenames, notes, column definitions, refresh logs and change explanations. Without those words, a correct result can become hard to reproduce.

A practical example

A team presents a geographic market comparison, but no one knows when the source values were updated. Adding a refresh note and preserving the prior snapshot makes later review possible.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

A tidy audit note does not validate the source by itself. Review methodology and authority according to the decision’s stakes.

• Record refresh date and operator.
• Preserve prior snapshots.
• Describe transformations.
• Link to the primary source for consequential claims.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter

Chapter 17 of 17: The final checklist separates entity, field, time and claim

The mechanism

Before sharing a linked-data workbook, review four layers: the matched entity, extracted field, refresh time and sentence built from the value. Each can be correct or wrong independently.

This is where English becomes a quality-control system. A precise sentence forces the analyst to reveal scope, comparison and limit rather than hiding behind a number.

A practical example

The workbook’s values are accurate, but the caption says they are “current” without a date. A final language review adds the retrieval date and removes an unsupported forecast.

A strong spreadsheet explanation names the entity, field, unit, source and time before it offers an interpretation. That sentence acts like a checksum: if one part cannot be stated, the analysis probably needs another inspection.

Limits and practical action

No checklist makes online data permanent or complete. The aim is traceable, proportionate use, not false certainty.

• Confirm every ambiguous entity.
• Check fields and units.
• Stamp the refresh time.
• Rewrite claims to match the evidence.

Try a transfer exercise: write one caption for the value before refresh and one after refresh. Then explain exactly what changed and what did not. This builds both data literacy and precise English without pretending the software has answered the research question.

Back to reading routes · Previous chapter

Advice for students, parents and educators

For students

Keep the original text, matched entity and extracted fields visible while learning. Open the card, read the provider, date your refresh and use cautious language for changing values. A neat chart is useful only when its categories remain meaningful.

For parents

Ask your child to explain why the cell icon matters and how two places or companies with similar names can be confused. The goal is not financial prediction. It is the habit of checking identity, source, time and claim before trusting a number.

For teachers and tutors

Use linked data types to teach comparison, not merely convenience. Require a small data dictionary, a refresh note, one official-source check and a limitation paragraph. These additions turn a button-clicking exercise into disciplined research.

Did You Know? Linked-data discoveries

• The Stocks button can represent more than ordinary company shares, including several other financial instrument types documented by Microsoft.
• A question-mark icon can mean Excel needs the user to resolve an ambiguous entity.
• The data card includes field-value pairs and a source note.
• Refresh All can update more than the selected linked cells, including other workbook connections.
• A linked entity can be referenced by formulas using named fields.
• Older or unsupported Excel versions may not preserve the interactive linked-data experience.

Frequently asked questions

Is a linked data type just formatted text?

No. It connects the cell to an online entity and exposes named fields. The visible label may look similar to the original text, so check the icon and card.

Why does Excel show a question mark?

It usually means the text has not been matched confidently. Correct spelling, add context and use the selector to choose the intended entity.

Are Stocks values real time?

Do not assume so. Read the source and field information, note the refresh time and follow official market documentation when timing is consequential.

Can I use linked stock data as investment advice?

No. It can support learning and analysis, but it does not guarantee accuracy, suitability or future performance.

What does Refresh All change?

It may update all linked data types and other workbook connections, queries or PivotTables. Save a version and check downstream results.

Why can two users see different results?

Account, edition, platform, editing language, refresh time, connection and organisational policy can differ.

Should I cite Excel or the provider?

For substantive claims, cite the underlying authoritative source and record the retrieval date. Excel is the tool that displayed or connected the field.

How do I compare cities fairly?

Check that the entities use compatible geographic boundaries and field definitions. City proper and metropolitan area are not interchangeable.

What if a field is missing?

Inspect the entity and source. Report missing data honestly rather than inserting a guessed value.

Does English matter if the task is numerical?

Yes. English defines entities, fields, units, time, comparisons and limits—the structure that makes a number interpretable.

Useful next reading and checked sources

Use Microsoft’s current documentation for feature behaviour and primary statistical or market sources for consequential claims. The eduKate links below extend the English and study-skills route.

• Microsoft Support: Excel data types — Stocks and Geography
• Microsoft Support: What linked data types are available?
• Microsoft Support: Automatically refresh linked data types
• Microsoft Support: Linked data type refresh errors
• MOE: EdTech Masterplan
• IMDA: Digital Skills for Life
• eduKateSG: How English Works — Explanation
• SETC: Study Skills for Secondary School English
• eduKateSingapore: Why English Matters in Singapore

English is a bridge for documenting the spreadsheet’s meaning. It complements mathematical, geographic, financial and multilingual knowledge; it does not replace them. The best workbook lets readers recover the reasoning in the language and sources appropriate to the task.