[{"data":1,"prerenderedAt":1103},["ShallowReactive",2],{"\u002Fblog\u002Fsharepoint-register-fields-and-data-checks":3},{"id":4,"title":5,"author":6,"body":7,"category":1083,"date":1084,"description":1085,"draft":1086,"excerpt":1087,"extension":1088,"heroImage":1089,"heroImageAlt":1090,"meta":1091,"navigation":1092,"path":1093,"seo":1094,"seoTitle":1087,"slug":1087,"stem":1095,"tags":1096,"updated":1087,"__hash__":1102},"blog\u002Fblog\u002Fsharepoint-register-fields-and-data-checks.md","SharePoint Register Validation: A Worked Example of Field Settings and Tests","QikSolve",{"type":8,"value":9,"toc":1067},"minimark",[10,23,32,35,42,45,50,60,63,112,126,130,133,161,164,169,187,240,266,276,289,293,300,338,362,368,372,383,441,457,463,467,482,534,550,554,573,580,590,597,602,605,615,619,622,695,698,701,704,852,858,861,865,868,871,874,907,910,922,926,929,1042,1049,1052,1056,1059],[11,12,13,20],"blockquote",{},[14,15,16],"p",{},[17,18,19],"strong",{},"What you'll take away",[14,21,22],{},"A worked SharePoint quality-register design with column types, suggested settings and a\npre-test checklist to adapt before moving beyond Excel. This article prepares the tests;\nthe follow-up reviews the SharePoint results.",[14,24,25,26,31],{},"This article is part of the SharePoint quality-register validation series. It develops the\nfield-design and pre-test stage of\n",[27,28,30],"a",{"href":29},"\u002Fblog\u002Fvalidating-a-sharepoint-quality-register\u002F","Validating a SharePoint Quality Register: A Worked Example",".\nThat guide covers the wider computerised system validation (CSV) approach; this instalment\nfocuses on column settings and the tests planned to assess them.",[14,33,34],{},"For quality assurance (QA) and operations teams moving a quality register out of Excel, SharePoint Lists is an option\nto assess for GxP use. The work goes beyond data migration: field definitions, ownership and\ntest evidence need to support the register's intended role in the quality process.",[14,36,37,38,41],{},"This guide provides a real-world example of some of the options you might use when configuring\na SharePoint quality register. It uses a ",[17,39,40],{},"fictional deviation register"," to illustrate column\ntypes, required fields, unique identifiers, controlled choices, accountable owners and date rules,\nwith a pre-test plan setting out the expected outcomes to check in SharePoint.\nThe controlled deviation record remains authoritative; the list tracks its reference, owner,\ndates and status.",[14,43,44],{},"The practical output is a reviewable specification linking each proposed control to a test,\nso the process owner and list owner can agree what to build and what evidence to collect.\nA follow-up article will review the observed SharePoint results and any changes needed.\nThis article covers preparation rather than execution; assess the wider GxP requirements\nfor your intended use with the process owner.",[46,47,49],"h2",{"id":48},"_1-define-the-test-setup-and-agree-the-rules","1. Define the test setup and agree the rules",[14,51,52,53,59],{},"Agree the vocabulary, identifier format, date rules and responsibilities with the process owner.\nAssign a list owner with permission to manage columns, and use a separate test list with synthetic\nrecords. Assess changes to existing operational lists through change control:\n",[27,54,58],{"href":55,"rel":56},"https:\u002F\u002Fsupport.microsoft.com\u002Fen-us\u002Fsharepoint\u002Flists\u002Fdata-and-lists\u002Flist-and-library-column-types-and-options",[57],"nofollow","Microsoft notes that changing a column type can corrupt existing data",".",[14,61,62],{},"For this example, agree these rules first:",[64,65,66,75,78,103,106],"ul",{},[67,68,69,70,74],"li",{},"Each register row has one manually assigned identifier, such as ",[71,72,73],"code",{},"DEV-2026-0001",", unique within this list.",[67,76,77],{},"Each row references an existing controlled deviation record. Multiple register rows may reference the same source record.",[67,79,80,81,84,85,88,89,92,93,84,96,88,99,102],{},"Status is ",[71,82,83],{},"Open",", ",[71,86,87],{},"In progress"," or ",[71,90,91],{},"Closed","; classification is ",[71,94,95],{},"Minor",[71,97,98],{},"Major",[71,100,101],{},"Critical",". These are illustrative labels, not regulatory definitions.",[67,104,105],{},"Opened date, due date and one accountable person are required. Due date cannot precede opened date.",[67,107,108,109,111],{},"Closure date is optional while work is open, but required when status is ",[71,110,91],{},". Any entered closure date cannot precede opened date.",[14,113,114,115,59],{},"Use the following column names exactly while following the example. Record the actual internal\u002FAPI\nnames separately if integrations use them: Microsoft Learn distinguishes a column's\n",[27,116,119,122,123],{"href":117,"rel":118},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fgraph\u002Fapi\u002Fresources\u002Fcolumndefinition?view=graph-rest-1.0",[57],[71,120,121],{},"name"," from its user-facing ",[71,124,125],{},"displayName",[46,127,129],{"id":128},"_2-specify-the-column-types-and-settings","2. Specify the column types and settings",[14,131,132],{},"Use the following as the build specification for the test list when you are ready to configure it.",[14,134,135,136,139,140,143,144,147,148,151,152,155,156,59],{},"In the list, select ",[17,137,138],{},"+ Add column",", choose the type, enter its name and settings, then save.\nUse ",[17,141,142],{},"More options"," where shown. For additional types, Microsoft documents ",[17,145,146],{},"Add column > See all\ncolumn types",". To inspect an existing column, open ",[17,149,150],{},"Settings > List settings",", then select it\nunder ",[17,153,154],{},"Columns",". Labels and available controls can differ between modern and classic screens;\nsee ",[27,157,160],{"href":158,"rel":159},"https:\u002F\u002Fsupport.microsoft.com\u002Fen-us\u002Fsharepoint\u002Flists\u002Fdata-and-lists\u002Fcreate-a-column-in-a-list-or-library",[57],"Microsoft's column-creation instructions",[14,162,163],{},"The Microsoft Learn references below describe SharePoint column properties through Microsoft Graph\nv1.0. You can apply the proposed settings through the list interface; API property names are\nincluded to help you trace each setting to its documentation.",[165,166,168],"h3",{"id":167},"single-line-of-text-summary-identifier-and-record-reference","Single line of text: summary, identifier and record reference",[14,170,171,172,175,176,179,180,183,184,59],{},"Use the existing ",[17,173,174],{},"Title"," column for a short summary; there is no need to create a second summary\ncolumn. Add ",[71,177,178],{},"RecordID"," and ",[71,181,182],{},"ControlledRecordRef"," as ",[17,185,186],{},"Single line of text",[188,189,190,206],"table",{},[191,192,193],"thead",{},[194,195,196,200,203],"tr",{},[197,198,199],"th",{},"Column",[197,201,202],{},"Settings for this example",[197,204,205],{},"Description to show users",[207,208,209,220,230],"tbody",{},[194,210,211,214,217],{},[212,213,174],"td",{},[212,215,216],{},"Required: Yes; maximum characters: 150; no default",[212,218,219],{},"Brief summary of the deviation; keep investigation details in the controlled record.",[194,221,222,224,227],{},[212,223,178],{},[212,225,226],{},"Required: Yes; enforce unique values: Yes; maximum characters: 13; no default",[212,228,229],{},"Assigned register ID in DEV-YYYY-NNNN format, for example DEV-2026-0001.",[194,231,232,234,237],{},[212,233,182],{},[212,235,236],{},"Required: Yes; enforce unique values: No; maximum characters: 100; no default",[212,238,239],{},"Exact identifier of the authoritative controlled deviation record.",[14,241,242,247,248,179,251,254,255,247,259,84,262,265],{},[27,243,246],{"href":244,"rel":245},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fgraph\u002Fapi\u002Fresources\u002Ftextcolumn?view=graph-rest-1.0",[57],"Microsoft Learn's text-column reference","\ndocuments ",[71,249,250],{},"maxLength",[71,252,253],{},"allowMultipleLines","; its\n",[27,256,258],{"href":117,"rel":257},[57],"column-definition reference",[71,260,261],{},"required",[71,263,264],{},"enforceUniqueValues"," and defaults. Single-line text supports up to 255\ncharacters, as explained in the linked Microsoft Support column-type guide; the smaller limits\nabove are deliberate example settings.",[14,267,268,269,271,272,275],{},"Keep ",[71,270,73],{}," as text, not Number: its prefix, separators and leading zeros are meaningful.\nThe 13-character maximum is ",[17,273,274],{},"not a format check","; it still permits shorter or incorrectly\nstructured values. Check the agreed pattern separately through a supported validation rule or a\nreview assigned to a named person before relying on the ID. These settings use manually assigned IDs.",[14,277,278,279,281,282,284,285,288],{},"Uniqueness checks for ",[71,280,178],{}," concern this column in this list, not identifiers across every\nsystem. A required ",[71,283,182],{}," only requires a value; reconcile it with the authoritative\nrecord to establish that it is the right reference. If users also need a clickable destination,\nconsider a separate ",[17,286,287],{},"Hyperlink"," column alongside the controlled-record identifier.",[165,290,292],{"id":291},"choice-status-and-classification","Choice: status and classification",[14,294,295,296,299],{},"Use ",[17,297,298],{},"Choice"," rather than free text where the process requires a controlled vocabulary.",[188,301,302,314],{},[191,303,304],{},[194,305,306,308,311],{},[197,307,199],{},[197,309,310],{},"Choices",[197,312,313],{},"Other settings for this example",[207,315,316,327],{},[194,317,318,321,324],{},[212,319,320],{},"Status",[212,322,323],{},"Open; In progress; Closed",[212,325,326],{},"Required: Yes; single selection; dropdown; allow manual\u002Ffill-in values: No; default: Open",[194,328,329,332,335],{},[212,330,331],{},"Classification",[212,333,334],{},"Minor; Major; Critical",[212,336,337],{},"Required: Yes; single selection; dropdown; allow manual\u002Ffill-in values: No; default: None",[14,339,340,345,346,349,350,353,354,357,358,361],{},[27,341,344],{"href":342,"rel":343},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fgraph\u002Fapi\u002Fresources\u002Fchoicecolumn?view=graph-rest-1.0",[57],"Microsoft Learn's choice-column reference","\ndocuments the values (",[71,347,348],{},"choices","), manual entry (",[71,351,352],{},"allowTextEntry",") and presentation (",[71,355,356],{},"displayAs",").\nIn the modern interface, the manual-entry setting may be labelled ",[17,359,360],{},"Can add values manually",".\nTurn it off for both columns and use single selection so each record has one status and\none classification.",[14,363,364,365,367],{},"An ",[71,366,83],{}," default reflects the starting state in this example. Classification has no default so\nthe person entering the record must select a category. Define closure authority and approval\nsteps separately from the available status labels.",[165,369,371],{"id":370},"date-and-time-opened-due-and-closure-dates","Date and time: opened, due and closure dates",[14,373,374,375,378,379,382],{},"Choose ",[17,376,377],{},"Date and time"," as the column type and ",[17,380,381],{},"Date only"," as the format for this\ncalendar-day example.",[188,384,385,400],{},[191,386,387],{},[194,388,389,391,394,397],{},[197,390,199],{},[197,392,393],{},"Required",[197,395,396],{},"Format and default",[197,398,399],{},"Rule",[207,401,402,416,428],{},[194,403,404,407,410,413],{},[212,405,406],{},"OpenedDate",[212,408,409],{},"Yes",[212,411,412],{},"Date only; no default",[212,414,415],{},"Enter the actual opened date from the controlled record.",[194,417,418,421,423,425],{},[212,419,420],{},"DueDate",[212,422,409],{},[212,424,412],{},[212,426,427],{},"Must be on or after OpenedDate.",[194,429,430,433,436,438],{},[212,431,432],{},"ClosureDate",[212,434,435],{},"No",[212,437,412],{},[212,439,440],{},"Required for Closed status; when entered, must be on or after OpenedDate.",[14,442,443,448,449,452,453,456],{},[27,444,447],{"href":445,"rel":446},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fgraph\u002Fapi\u002Fresources\u002Fdatetimecolumn?view=graph-rest-1.0",[57],"Microsoft Learn's date\u002Ftime reference","\ndistinguishes ",[71,450,451],{},"dateOnly"," from ",[71,454,455],{},"dateTime",", and standard date display from friendly relative display.\nPrefer a standard date display where available so users see a date rather than a relative label.\nInclude the site's regional settings and any integration's date conversion in the test plan,\nincluding exports and API entry paths where used.",[14,458,459,460,462],{},"Leave defaults blank deliberately. Today's entry date may not be the event's opened date,\nand a default closure date could make an incomplete record appear closed. Keep ",[71,461,432],{},"\noptional at column level: making it always required would prevent the intended open-record state.\nThe conditional requirement belongs in the list rule below. If your process needs event times,\nupdate all three definitions and their tests together.",[165,464,466],{"id":465},"person-or-group-accountable-owner","Person or Group: accountable owner",[14,468,469,470,473,474,477,478,481],{},"Create ",[71,471,472],{},"Owner"," using ",[17,475,476],{},"Person or Group"," (shown as ",[17,479,480],{},"Person"," in some modern menus).",[188,483,484,494],{},[191,485,486],{},[194,487,488,491],{},[197,489,490],{},"Setting",[197,492,493],{},"Value for this example",[207,495,496,503,510,518,526],{},[194,497,498,501],{},[212,499,500],{},"Require information",[212,502,409],{},[194,504,505,508],{},[212,506,507],{},"Allow multiple selections",[212,509,435],{},[194,511,512,515],{},[212,513,514],{},"Allow selection of",[212,516,517],{},"People only, not people and groups",[194,519,520,523],{},[212,521,522],{},"Display",[212,524,525],{},"Name",[194,527,528,531],{},[212,529,530],{},"Default",[212,532,533],{},"None",[14,535,536,247,541,84,544,179,547,549],{},[27,537,540],{"href":538,"rel":539},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fgraph\u002Fapi\u002Fresources\u002Fpersonorgroupcolumn?view=graph-rest-1.0",[57],"Microsoft Learn's person\u002Fgroup reference",[71,542,543],{},"allowMultipleSelection",[71,545,546],{},"chooseFromType",[71,548,356],{},". The proposed settings give\neach item one named accountable person rather than a free-text name or group assignment.\nSelecting an owner does not grant that person access or send a notification by itself.\nDefine reassignment for leave, role changes and departed users; test access and any reminders separately.",[46,551,553],{"id":552},"_3-prepare-the-cross-field-date-and-closure-rule","3. Prepare the cross-field date and closure rule",[14,555,556,557,560,561,566,567,572],{},"Required fields and choice settings address individual values. To check relationships between\nfields, use a list-level formula in ",[17,558,559],{},"List settings > Validation settings",". A calculated column\ndisplays a result rather than serving as this save-time check. Microsoft Learn documents a\n",[27,562,565],{"href":563,"rel":564},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fsharepoint\u002Fdev\u002Fschema\u002Fvalidation-element-list",[57],"list validation element",";\nMicrosoft's ",[27,568,571],{"href":569,"rel":570},"https:\u002F\u002Fsupport.microsoft.com\u002Fen-us\u002Fsharepoint\u002Flists\u002Fdata-and-lists\u002Fexamples-of-common-formulas-in-lists",[57],"formula examples","\nexplain the logical and blank-check functions used here.",[14,574,575,576,579],{},"For the exact column names and single-select Status above, this is a ",[17,577,578],{},"candidate formula to test",":",[581,582,588],"pre",{"className":583,"code":585,"language":586,"meta":587},[584],"language-text","=AND([DueDate]>=[OpenedDate],OR([Status]\u003C>\"Closed\",NOT(ISBLANK([ClosureDate]))),OR(ISBLANK([ClosureDate]),[ClosureDate]>=[OpenedDate]))\n","text","",[71,589,585],{"__ignoreMap":587},[14,591,592,593,596],{},"Set a clear ",[17,594,595],{},"User message",", for example:",[11,598,599],{},[14,600,601],{},"Due date must be on or after opened date. Closed items need a closure date. Any closure date must be on or after opened date.",[14,603,604],{},"The three parts are intended to check due-date order, the conditional closure requirement and\nclosure-date order. The intended logic permits an open item with a blank closure date and\nsame-day dates. It leaves future-date checks, closure dates on open items and approval of status\ntransitions outside this rule. Decide whether your process needs additional controls for those cases.",[14,606,607,608,84,610,179,612,614],{},"Keep requiredness enabled for ",[71,609,406],{},[71,611,420],{},[71,613,320],{},"; the formula is not a substitute\nfor those settings. Check the formula editor accepts the expression in your environment, including\ncolumn names and locale-specific separators. If a list already has a validation rule, combine\nthe requirements and retain the existing checks. Confirm the rule's behaviour by running its\npositive, negative and boundary cases in the target list.",[46,616,618],{"id":617},"_4-write-the-test-cases-before-running-them","4. Write the test cases before running them",[14,620,621],{},"Use this baseline for the planned tests, with a matching synthetic controlled record:",[188,623,624,633],{},[191,625,626],{},[194,627,628,630],{},[197,629,199],{},[197,631,632],{},"Synthetic value",[207,634,635,642,648,655,661,667,674,681,688],{},[194,636,637,639],{},[212,638,174],{},[212,640,641],{},"Training record reference missing",[194,643,644,646],{},[212,645,178],{},[212,647,73],{},[194,649,650,652],{},[212,651,182],{},[212,653,654],{},"TEST-DEV-0001",[194,656,657,659],{},[212,658,320],{},[212,660,83],{},[194,662,663,665],{},[212,664,331],{},[212,666,95],{},[194,668,669,671],{},[212,670,406],{},[212,672,673],{},"2026-11-02",[194,675,676,678],{},[212,677,420],{},[212,679,680],{},"2026-11-16",[194,682,683,685],{},[212,684,432],{},[212,686,687],{},"Leave blank",[194,689,690,692],{},[212,691,472],{},[212,693,694],{},"A designated test user with the intended access",[14,696,697],{},"Dates above use year-month-day notation for clarity; use the date picker and confirm the stored\nvalues. Save, reopen and compare every value with the baseline. Then change one thing at a time,\nrestoring the baseline between tests. Use another unique ID whenever creating another valid item.",[14,699,700],{},"Before execution, list the ways a record can be created or changed in your environment. Include\nonly routes that are enabled or permitted, such as the standard form, grid editing, an import,\nan approved flow, or an API integration. Record who can use each route and what controls or\nprocedures are expected to apply. Include checks for fields hidden in a form but accessible\nthrough other permitted entry paths.",[14,702,703],{},"Record the configuration and user context for each test. Agree whether each control should\nprevent an invalid entry or detect it for correction before use; these require different\nexpected outcomes.",[188,705,706,719],{},[191,707,708],{},[194,709,710,713,716],{},[197,711,712],{},"Test input or action",[197,714,715],{},"Expected outcome for the proposed configuration",[197,717,718],{},"Actual result",[207,720,721,732,742,752,762,772,782,792,802,812,822,832,842],{},[194,722,723,726,729],{},[212,724,725],{},"Save the complete Open baseline with ClosureDate blank",[212,727,728],{},"Save succeeds; values survive reopening; reference matches the synthetic source record",[212,730,731],{},"Not tested",[194,733,734,737,740],{},[212,735,736],{},"Omit each required field separately, including Title and Owner",[212,738,739],{},"Save is rejected with a useful required-field message",[212,741,731],{},[194,743,744,747,750],{},[212,745,746],{},"Create another item with RecordID DEV-2026-0001",[212,748,749],{},"Duplicate is rejected",[212,751,731],{},[194,753,754,757,760],{},[212,755,756],{},"Enter more than 13 characters in RecordID",[212,758,759],{},"Entry is limited or rejected; stored value is not silently accepted as a different identifier",[212,761,731],{},[194,763,764,767,770],{},[212,765,766],{},"Enter a short but unique ID such as BAD",[212,768,769],{},"Without a separate pattern rule it may save; the assigned review identifies the invalid format",[212,771,731],{},[194,773,774,777,780],{},[212,775,776],{},"Try an unlisted Status or Classification value",[212,778,779],{},"Manual value cannot be saved as an accepted choice",[212,781,731],{},[194,783,784,787,790],{},[212,785,786],{},"Set DueDate to 2026-11-01",[212,788,789],{},"Save is rejected by the date rule",[212,791,731],{},[194,793,794,797,800],{},[212,795,796],{},"Set DueDate equal to OpenedDate",[212,798,799],{},"Save succeeds; same-day deadlines are permitted in this example",[212,801,731],{},[194,803,804,807,810],{},[212,805,806],{},"Set Status to Closed with ClosureDate blank",[212,808,809],{},"Save is rejected by the closure rule",[212,811,731],{},[194,813,814,817,820],{},[212,815,816],{},"Enter ClosureDate 2026-11-01, with either Open or Closed status",[212,818,819],{},"Save is rejected because closure precedes opening",[212,821,731],{},[194,823,824,827,830],{},[212,825,826],{},"Set Status to Closed and ClosureDate equal to OpenedDate",[212,828,829],{},"Save succeeds if all other values are valid",[212,831,731],{},[194,833,834,837,840],{},[212,835,836],{},"Try to assign two people or a group to Owner",[212,838,839],{},"Selection is constrained to one person",[212,841,731],{},[194,843,844,847,850],{},[212,845,846],{},"Enter a plausible but incorrect ControlledRecordRef",[212,848,849],{},"A nonblank value may save; source reconciliation must identify the mismatch",[212,851,731],{},[14,853,854,855,857],{},"Repeat applicable tests through each permitted entry path, including any relevant boundary cases\nsuch as an existing item being edited, an import being corrected, or a flow updating a record.\nAll actual results deliberately remain ",[17,856,731],{}," in this pre-test plan. During execution,\nrecord the observed outcome, including any difference from the expected result.",[14,859,860],{},"If one path accepts a value another path rejects, record the difference as a control gap. Decide\nwhether to restrict that route, add a suitable check, or manage the residual risk with an owned\nprocedure. A successful test in one form covers that entry path, not every enabled route.",[46,862,864],{"id":863},"_5-define-the-evidence-to-capture","5. Define the evidence to capture",[14,866,867],{},"For the follow-up results review, capture the configured column settings and accepted formula,\nthe test date, regional\u002Ftime-zone settings, user permissions and entry path. Give each executed\ncase a test ID and retain its input, expected outcome, observed outcome and a screenshot or other\nevidence reference. Keep screenshots limited to the test list and synthetic data.",[14,869,870],{},"If a setting is unavailable or a formula is rejected, record that as a result too. Document\nany correction and its retest separately so the review distinguishes the original design from\nthe observed behaviour. The follow-up should explain both successful controls and remaining gaps.",[14,872,873],{},"For each critical field or rule, retain a short trace from requirement to evidence:",[875,876,877,883,889,895,901],"ol",{},[67,878,879,882],{},[17,880,881],{},"Requirement:"," what the field must represent and why it matters.",[67,884,885,888],{},[17,886,887],{},"Failure:"," a foreseeable incorrect, missing or misleading value.",[67,890,891,894],{},[17,892,893],{},"Control:"," the configured setting or procedure intended to prevent or detect it.",[67,896,897,900],{},[17,898,899],{},"Verification:"," the test, entry path, expected result and actual result.",[67,902,903,906],{},[17,904,905],{},"Owner:"," who approves the rule, reviews exceptions and maintains it after change.",[14,908,909],{},"Keep the dictionary, relevant list settings, test records and unresolved limitations together under\nthe organisation's document-control practices. Reassess the controls when the register's purpose,\nfield definitions, permissions, integrations or entry routes change. A choice list can constrain\nlabels without authorising a status transition; a required field can require an answer without\nproving that answer is correct.",[14,911,912,913,917,918,59],{},"Where the register informs regulated quality decisions, assess its intended use and risks within\nthe applicable quality system. Place these field checks within the wider validation and\nchange-control work. For broader assurance context, see\n",[27,914,916],{"href":915},"\u002Fblog\u002Fvalidating-a-sharepoint-quality-register","validating a SharePoint quality register","\nand the ",[27,919,921],{"href":920},"\u002Fblog\u002Fbeyond-excel-gxp-quality-registers-sharepoint-lists","quality-register overview",[46,923,925],{"id":924},"sources-and-scope","Sources and scope",[14,927,928],{},"Microsoft documentation checked on 10 November 2026:",[188,930,931,941],{},[191,932,933],{},[194,934,935,938],{},[197,936,937],{},"Source",[197,939,940],{},"What it supports here",[207,942,943,954,965,976,987,998,1009,1020,1031],{},[194,944,945,951],{},[212,946,947],{},[27,948,950],{"href":117,"rel":949},[57],"Microsoft Learn: columnDefinition, Graph v1.0",[212,952,953],{},"Column names, descriptions, requiredness, defaults and uniqueness properties",[194,955,956,962],{},[212,957,958],{},[27,959,961],{"href":244,"rel":960},[57],"Microsoft Learn: textColumn, Graph v1.0",[212,963,964],{},"Text length and multiline settings",[194,966,967,973],{},[212,968,969],{},[27,970,972],{"href":342,"rel":971},[57],"Microsoft Learn: choiceColumn, Graph v1.0",[212,974,975],{},"Allowed choices, manual entry and display options",[194,977,978,984],{},[212,979,980],{},[27,981,983],{"href":445,"rel":982},[57],"Microsoft Learn: dateTimeColumn, Graph v1.0",[212,985,986],{},"Date-only\u002Fdate-time format and standard\u002Ffriendly display",[194,988,989,995],{},[212,990,991],{},[27,992,994],{"href":538,"rel":993},[57],"Microsoft Learn: personOrGroupColumn, Graph v1.0",[212,996,997],{},"Single\u002Fmultiple selection, people-only selection and name display",[194,999,1000,1006],{},[212,1001,1002],{},[27,1003,1005],{"href":563,"rel":1004},[57],"Microsoft Learn: Validation element (List)",[212,1007,1008],{},"List validation schema and message; not verification of the example formula",[194,1010,1011,1017],{},[212,1012,1013],{},[27,1014,1016],{"href":158,"rel":1015},[57],"Microsoft Support: create a column",[212,1018,1019],{},"UI creation steps, additional settings and validation availability",[194,1021,1022,1028],{},[212,1023,1024],{},[27,1025,1027],{"href":55,"rel":1026},[57],"Microsoft Support: column types and options",[212,1029,1030],{},"User-facing type\u002Fsettings guidance, single-line limit and type-change warning",[194,1032,1033,1039],{},[212,1034,1035],{},[27,1036,1038],{"href":569,"rel":1037},[57],"Microsoft Support: common formulas",[212,1040,1041],{},"Logical, comparison and blank-check formula building blocks",[14,1043,1044,1045,1048],{},"The settings, vocabulary, character limits and combined formula are proposed for this example,\nrather than prescribed by Microsoft. Available settings and API responses need to be checked\nin the target environment. For example, the column-definition reference notes that site\u002Flist\ncolumn responses omit its ",[71,1046,1047],{},"validation"," property. Inspect the validation settings separately\nwhen recording the configuration.",[14,1050,1051],{},"No SharePoint tenant configuration or formula execution was performed for this article. The guide\ndoes not determine regulatory applicability or claim that these settings establish GMP compliance.\nAny interpretation of Good Manufacturing Practice (GMP) requirements needs a separate review\nof the applicable sources by a qualified reviewer.",[46,1053,1055],{"id":1054},"next-step","Next step",[14,1057,1058],{},"Agree this configuration and its expected outcomes before running the tests. The follow-up\narticle will use the SharePoint results to review which controls behaved as expected, where\nthe design needed adjustment and what still requires a procedural check.",[14,1060,1061,1062,1066],{},"If you are assessing a move from a spreadsheet, use the ",[27,1063,1065],{"href":1064},"\u002Fsolutions\u002Fexcel-register-to-sharepoint","Excel register migration and validation\nsign-off pack"," to frame the wider decision and handoff.\nKeep this field dictionary and test plan aligned with the register's intended use.",{"title":587,"searchDepth":1068,"depth":1068,"links":1069},2,[1070,1071,1078,1079,1080,1081,1082],{"id":48,"depth":1068,"text":49},{"id":128,"depth":1068,"text":129,"children":1072},[1073,1075,1076,1077],{"id":167,"depth":1074,"text":168},3,{"id":291,"depth":1074,"text":292},{"id":370,"depth":1074,"text":371},{"id":465,"depth":1074,"text":466},{"id":552,"depth":1068,"text":553},{"id":617,"depth":1068,"text":618},{"id":863,"depth":1068,"text":864},{"id":924,"depth":1068,"text":925},{"id":1054,"depth":1068,"text":1055},"Compliance","2026-11-10","Prepare a SharePoint quality-register test plan with column types, proposed settings and expected results for required fields, duplicate IDs and date rules.",false,null,"md","\u002Fimages\u002Fblog\u002Fqiksolve-blog-sharepoint-register-fields-abstract-1200x900.webp","Nested blue and grey rectangular frames beside abstract architectural forms on a light background.",{},true,"\u002Fblog\u002Fsharepoint-register-fields-and-data-checks",{"title":5,"description":1085},"blog\u002Fsharepoint-register-fields-and-data-checks",[1097,1098,1099,1100,1101],"sharepoint","quality-register","data-validation","data-integrity","metadata","SxeKddT5t-RyqBLMfTRkuv_huCzqOpOY5K19jv3VOPs",1794281268886]