Update from source repository (workflow run: 15785827441) (PR #14126) (commit: 6f4bad057ddcf4dc5eb8b2e5828831fbc743a272) (branch: 10.10.0.cl)

Author: GitHub Action Sync Bot

cloud/modules/ROOT/pages/tml.adoc

@@ -45,6 +45,15 @@ obj_id: <unique_string>
 
 When you migrate an object between clusters, use the `obj_id` as the primary method of import.
 
+[#fqn]
+=== fqn
+
+fqn refers to the source table's GUID. You can find this string of letters and numbers at the end of the URL for that table or connection.
+
+For example, in `https://<company>.thoughtspot.com/#/data/tables/34226aaa-4bcf-4d6b-9045-24cb1e9437cb`, the GUID is `34226aaa-4bcf-4d6b-9045-24cb1e9437cb`.
+
+Use this optional parameter to reduce ambiguity and identify a specific table, if you have multiple tables with the same name. When exporting a TML file, you have the option to *Export FQNs of referenced objects*, which ensures that the TML files you export contain FQNs for the underlying tables and connections. If you do not add the `fqn` parameter, and the connection or table you reference does not have a unique name, the file import fails.
+
 == Limitations of working with TML files
 
 There are certain limitations to the changes you can apply by editing a Worksheet, Answer, table, view, Liveboard, or xref:monitor.adoc[Monitor alert] through TML.