Analytica Docs - Recent changes [en]

In-memory binary data terms

Lchrisman — Mon, 21 Sep 2026 18:01:16 GMT

table format fix, | should have been ||

← Older revision		Revision as of 18:01, 21 September 2026
Line 58:		Line 58:
	\| base64 literal \|\| binary data term \|\| [[Base64-encoded_binary_term_literals\|<code>base64'....''</code>]] \|\| [[Analytica 6.2]]		\| base64 literal \|\| binary data term \|\| [[Base64-encoded_binary_term_literals\|<code>base64'....''</code>]] \|\| [[Analytica 6.2]]
	\|-		\|-
	\| base64 text \|\| binary data term \|\| <code>[[Evaluate]]( f"base64'{txt}'")</code> \| [[Analytica 6.2]]		\| base64 text \|\| binary data term \|\| <code>[[Evaluate]]( f"base64'{txt}'")</code> \|\| [[Analytica 6.2]]
	\|-		\|-
	\| base64 literal \|\| image \|\| <code>[[GetFromBinaryData]]( base64'...', typeFlags:8 )</code> \|\| [[Analytica 6.4]]		\| base64 literal \|\| image \|\| <code>[[GetFromBinaryData]]( base64'...', typeFlags:8 )</code> \|\| [[Analytica 6.4]]
Line 68:		Line 68:
	\| hexadecimal literal \|\| binary data term \|\| <code>base16'....''</code> \|\| [[Analytica 6.4]]		\| hexadecimal literal \|\| binary data term \|\| <code>base16'....''</code> \|\| [[Analytica 6.4]]
	\|-		\|-
	\| hexadecimal text \|\| binary data term \|\| <code>[[Evaluate]]( f"base16'{txt}'")</code> \| [[Analytica 6.4]]		\| hexadecimal text \|\| binary data term \|\| <code>[[Evaluate]]( f"base16'{txt}'")</code> \|\| [[Analytica 6.4]]
	\|-		\|-
	\| hexadecimal literal \|\| image \|\| <code>[[GetFromBinaryData]]( base16'...', typeFlags:8 )</code> \|\| [[Analytica 6.4]]		\| hexadecimal literal \|\| image \|\| <code>[[GetFromBinaryData]]( base16'...', typeFlags:8 )</code> \|\| [[Analytica 6.4]]

Help menu

Lchrisman — Mon, 21 Sep 2026 15:25:13 GMT

EW 22472 - new screenshot for Help menu in 7.2

← Older revision		Revision as of 15:25, 21 September 2026
Line 10:		Line 10:

	:{\| class="wikitable"		:{\| class="wikitable"
	\| rowspan="42" \| {{Release\|\|4.~~6\|[[Image:Menus_13.png]]}}{{Release\|5.0\|5.9~~\|[[Image: Help menu 5.0.png]]~~}}{{Release\|6.0\|~~\|[[Image:Help menu 6.0.png]]}}		\| rowspan="42" \| {{Release?\|7.2\|[[Image:Help menu 7.2.png]]\|[[Image:Help menu 6.0.png]]}}
	! style="width: 140px;" \| Menu item		! style="width: 140px;" \| Menu item
	! Description		! Description

File:Help menu 7.2.png

Lchrisman — Mon, 21 Sep 2026 15:24:37 GMT

Lchrisman uploaded File:Help menu 7.2.png updated 7.2 screenshot. Docs login info... has been removed. (EW 22472)

New page

== Summary ==
updated 7.2 screenshot. Docs login info... has been removed. (EW 22472)

Help menu

Lchrisman — Mon, 21 Sep 2026 15:21:44 GMT

EW 22472 - Removal of Docs login info... (Not used server-side any more)

← Older revision		Revision as of 15:21, 21 September 2026
Line 33:		Line 33:
	{{!}}Jumps to the [[What's new in Analytica {{#svarget:anarelease\|5.0}}?]] page.		{{!}}Jumps to the [[What's new in Analytica {{#svarget:anarelease\|5.0}}?]] page.
	}}		}}
	\|-		{{Release\|1=\|2=7.1\|3=
	\|{{Release\|\|6.2~~\|Wiki}}{{Release\|6.3\|\|Docs}} login info...~~
	~~\|Allows you to store or change your [[Special: UserLogin\|Analytica Docs login]] and password, so that when you click on a link to a {{Release\|\|6~~.~~2\|Wiki}}{{Release~~\|6.3~~\|\|Docs}} page (e.g., a “More information” link), Analytica can log you in automatically.~~
	~~{{Release\|6.0\|\|~~
	{{!}}-		{{!}}-
	{{!}}~~Analytica Q&A forum~~		{{!}}Docs login info...
	{{!}}~~The place to ask Analytica or modeling questions, browse what others have asked or shared, answer questions and share examples~~.		{{!}}'''''Deprecated:''''' This is no longer used by the docs server. You can log in from on the docs.}}
	}}
	\|-		\|-
	~~\|{{Release\|\|5.9\|Web tech support}}{{Release\|6.0\|~~\|Tech support instructions}}		\|Tech support instructions
	\|Opens your default web browser to the [https://analytica.com/support/technical-support/ Analytica Tech Support page] at https://analytica.com.		\|Opens your default web browser to the [https://analytica.com/support/technical-support/ Analytica Tech Support page] at https://analytica.com.
			\|-
			\|Analytica Q&A forum
			\|The place to ask Analytica or modeling questions, browse what others have asked or shared, answer questions and share examples.
	\|-		\|-
	\|Email tech support		\|Email tech support

Internal:Suan acceptance test script

Dpaine — Sun, 20 Sep 2026 22:44:54 GMT

Time out

Analytica Release Notes/Changes in Patch Build 7.1.13.328

Dpaine — Sun, 20 Sep 2026 13:59:23 GMT

← Older revision		Revision as of 13:59, 20 September 2026
Line 1:		Line 1:
	The 7.1.13 patch release fixes an important bug that can potentially result in an incorrect calculation in some cases.		The 7.1.13 patch release replaces the previous [[What's new in Analytica 7.1?\|7.1.12]] release.

			This patch fixes an important bug that can potentially result in an incorrect calculation in some cases.

			* An incorrect result for some IF-THEN-ELSE statements of the form '''If a Then b else Null''' .
			* Unnecessary "DawnCache" and "GPUCache" folders were being created in folders where a model was used with Assista.

Analytica Release Notes/Changes in Patch Build 7.1.13.328

Dpaine — Sun, 20 Sep 2026 13:42:23 GMT

Created page with "The 7.1.13 patch release fixes an important bug that can potentially result in an incorrect calculation in some cases."

New page

The 7.1.13 patch release fixes an important bug that can potentially result in an incorrect calculation in some cases.

Analytica 7.1 beta Release Notes

Dpaine — Sun, 20 Sep 2026 13:41:31 GMT

Notes for individual builds

← Older revision		Revision as of 13:41, 20 September 2026
(One intermediate revision by the same user not shown)
Line 8:		Line 8:

	== Notes for individual builds ==		== Notes for individual builds ==
			* [[Analytica_Release_Notes/Changes_in_Patch_Build_7.1.13.328\|Changes in 7.1.13]] ''patch.''
	* [[Analytica_7.1_beta_Release_Notes/Changes_in_7_1_11_323\|Changes in 7.1.11]] ''beta.''		* [[Analytica_7.1_beta_Release_Notes/Changes_in_7_1_11_323\|Changes in 7.1.11]] ''beta.''
	* [[Analytica_7.1_beta_Release_Notes/Changes_in_7_1_9_321\|Changes in 7.1.9]] ''beta.''		* [[Analytica_7.1_beta_Release_Notes/Changes_in_7_1_9_321\|Changes in 7.1.9]] ''beta.''

GoogleAccountEmail

Lchrisman — Fri, 18 Sep 2026 19:31:31 GMT

ER 21588: redirect to the GoogleSheets backend documentation

New page

#REDIRECT [[Functions To Read Excel Worksheets#SpreadsheetOpen]]

[[Category:Integration Functions]]

DisconnectGoogleAccount

Lchrisman — Fri, 18 Sep 2026 19:31:31 GMT

ER 21588: redirect to the GoogleSheets backend documentation

New page

#REDIRECT [[Functions To Read Excel Worksheets#SpreadsheetOpen]]

[[Category:Integration Functions]]

Functions To Read Excel Worksheets

Lchrisman — Fri, 18 Sep 2026 19:31:30 GMT

ER 21588: document GoogleAccountEmail / DisconnectGoogleAccount where readers actually land

← Older revision		Revision as of 19:31, 18 September 2026
Line 58:		Line 58:
	*; Advanced: Analytica identifies itself to Google as an application registered by Lumina. An organization that would rather it identified itself as an application of their own -- because their Google Workspace administrator controls which outside applications may reach their data, for example -- can arrange that; see [[Using your own Google OAuth client]], which also covers asking Google for access to every spreadsheet so that the chooser is never shown.		*; Advanced: Analytica identifies itself to Google as an application registered by Lumina. An organization that would rather it identified itself as an application of their own -- because their Google Workspace administrator controls which outside applications may reach their data, for example -- can arrange that; see [[Using your own Google OAuth client]], which also covers asking Google for access to every spreadsheet so that the chooser is never shown.
	*; Unattended use: A server, a scheduled job or [[Analytica Decision Engine\|ADE]] on a machine where nobody is present cannot answer a browser. Give «account» a Google service account instead, and share the spreadsheet with its e-mail address -- see [[Using a Google service account]].		*; Unattended use: A server, a scheduled job or [[Analytica Decision Engine\|ADE]] on a machine where nobody is present cannot answer a browser. Give «account» a Google service account instead, and share the spreadsheet with its e-mail address -- see [[Using a Google service account]].
			*; Managing the connection: <code>SysLib_Internal::GoogleAccountEmail()</code> answers the Google account Analytica is connected to, or Null when there is none. <code>SysLib_Internal::DisconnectGoogleAccount()</code> revokes that access at Google and forgets the stored connection, returning the address it disconnected; it is a side effect, so evaluate it from a button's OnClick or the [[Typescript Window\|Typescript window]] rather than in a Definition. Opening a spreadsheet again then reconnects, and <code>showDialog: True</code> forces the connect dialog if you want to switch accounts. You can also revoke Analytica's access from [https://myaccount.google.com/permissions your Google account's permissions page].
	}}		}}
	}}		}}

Category:Analytica MCP Platform

Lchrisman — Fri, 18 Sep 2026 18:07:15 GMT

Created page with "The Analytica MCP Platform (AMP) is a Lumina product offering that runs Analytica models headlessly while exposing a Model Context Protocol (MCP) API. It is designed especially for use cases involving a front-end language model interface. This category page lists pages specifically related to AMP."

New page

The Analytica MCP Platform (AMP) is a Lumina product offering that runs Analytica models headlessly while exposing a Model Context Protocol (MCP) API. It is designed especially for use cases involving a front-end language model interface.

This category page lists pages specifically related to AMP.

Using a Google service account

Lchrisman — Fri, 18 Sep 2026 18:01:37 GMT

categories ADE & AMP

← Older revision		Revision as of 18:01, 18 September 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	[[Category:Integration Functions]]		[[Category:Integration Functions]]
			[[Category:Analytica Decision Engine]]
			[[Category:Analytica MCP Platform]]

	{{ReleaseBar}}		{{ReleaseBar}}

			''New to [[Analytica 7.2]]''

	{{Release\|1=7.2\|2=\|3=		{{Release\|1=7.2\|2=\|3=

Using your own Google OAuth client

Lchrisman — Fri, 18 Sep 2026 16:24:46 GMT

← Older revision		Revision as of 16:24, 18 September 2026
Line 1:		Line 1:
	[[Category:Integration Functions]]		[[Category:Integration Functions]]
	{{ReleaseBar}}		{{ReleaseBar}}

			''Requires [[Analytica 7.2]]''

	{{Release\|1=7.2\|2=\|3=		{{Release\|1=7.2\|2=\|3=

Functions To Read Excel Worksheets

Lchrisman — Fri, 18 Sep 2026 15:47:06 GMT

ER 21588 Phase 4: link the service-account page (re-applying; a cached action=raw fetch reverted it)

← Older revision		Revision as of 15:47, 18 September 2026
(2 intermediate revisions by the same user not shown)
Line 8:		Line 8:

	<div id="SpreadsheetOpen" >		<div id="SpreadsheetOpen" >
	== SpreadsheetOpen(filename'', showDialog, title{{Release\|7.0\|\|, backend}}'') ==		== SpreadsheetOpen(filename'', showDialog, title{{Release\|7.0\|\|, backend}}{{Release\|7.2\|\|, account}}'') ==
	</div>		</div>

Line 56:		Line 56:
	*; Capabilities: Reads come from a snapshot taken when the workbook is opened. Writes made with [[SpreadsheetSetCell]] and [[SpreadsheetSetRange]], and sheets added or removed, are sent to Google when the computation finishes, when you call [[Functions_to_Write_Data_to_Excel_Worksheets#SpreadsheetSave\|SpreadsheetSave]](wb), or when the workbook is refreshed: <code>SpreadsheetSetInfo(wb, 'Refresh', true)</code> sends the pending writes and re-downloads the spreadsheet, so the values Google computed (and other people's edits) are seen. A native Google Sheet is exported by Google as an .xlsx snapshot (Google limits the export to 10 MB); an Excel workbook stored in Drive is downloaded as-is and written back as a whole file. The tab names the model sees (<code>SpreadsheetInfo(wb, 'Sheets')</code>, and «sheet» given by name) are the names in the exported snapshot, truncated to 31 characters, while writes are addressed to Google's real tab titles. <code>SpreadsheetOpen("New", backend:'GoogleSheets', title: "My sheet")</code> creates a new Google Sheet in your Drive. The second return value is the spreadsheet's link.		*; Capabilities: Reads come from a snapshot taken when the workbook is opened. Writes made with [[SpreadsheetSetCell]] and [[SpreadsheetSetRange]], and sheets added or removed, are sent to Google when the computation finishes, when you call [[Functions_to_Write_Data_to_Excel_Worksheets#SpreadsheetSave\|SpreadsheetSave]](wb), or when the workbook is refreshed: <code>SpreadsheetSetInfo(wb, 'Refresh', true)</code> sends the pending writes and re-downloads the spreadsheet, so the values Google computed (and other people's edits) are seen. A native Google Sheet is exported by Google as an .xlsx snapshot (Google limits the export to 10 MB); an Excel workbook stored in Drive is downloaded as-is and written back as a whole file. The tab names the model sees (<code>SpreadsheetInfo(wb, 'Sheets')</code>, and «sheet» given by name) are the names in the exported snapshot, truncated to 31 characters, while writes are addressed to Google's real tab titles. <code>SpreadsheetOpen("New", backend:'GoogleSheets', title: "My sheet")</code> creates a new Google Sheet in your Drive. The second return value is the spreadsheet's link.
	*; Return type: Returns a «GoogleSheetsWorkbook» object for a native Google Sheet, or a «LibXlWorkbook» object for an Excel file stored in Drive. <code>SpreadsheetInfo(wb, 'Backend')</code> returns <code>'GoogleSheets'</code> or <code>'LibXl'</code> accordingly, and <code>SpreadsheetInfo(wb, 'URL')</code> and <code>SpreadsheetInfo(wb, 'Account')</code> give its link and the Google account it was opened with.		*; Return type: Returns a «GoogleSheetsWorkbook» object for a native Google Sheet, or a «LibXlWorkbook» object for an Excel file stored in Drive. <code>SpreadsheetInfo(wb, 'Backend')</code> returns <code>'GoogleSheets'</code> or <code>'LibXl'</code> accordingly, and <code>SpreadsheetInfo(wb, 'URL')</code> and <code>SpreadsheetInfo(wb, 'Account')</code> give its link and the Google account it was opened with.
	*; Advanced: Analytica identifies itself to Google as an application registered by Lumina. An organization that would rather it identified itself as an application of their own -- because their Google Workspace administrator controls which outside applications may reach their data, for example -- can arrange that; see [[Using your own Google OAuth client]].		*; Advanced: Analytica identifies itself to Google as an application registered by Lumina. An organization that would rather it identified itself as an application of their own -- because their Google Workspace administrator controls which outside applications may reach their data, for example -- can arrange that; see [[Using your own Google OAuth client]], which also covers asking Google for access to every spreadsheet so that the chooser is never shown.
			*; Unattended use: A server, a scheduled job or [[Analytica Decision Engine\|ADE]] on a machine where nobody is present cannot answer a browser. Give «account» a Google service account instead, and share the spreadsheet with its e-mail address -- see [[Using a Google service account]].
	}}		}}
	}}		}}
Line 426:		Line 427:
	* [[Functions to Write Data to Excel Worksheets]] -- [[SpreadsheetSetCell]], [[SpreadsheetSetRange]] and [[SpreadsheetSave]]		* [[Functions to Write Data to Excel Worksheets]] -- [[SpreadsheetSetCell]], [[SpreadsheetSetRange]] and [[SpreadsheetSave]]
	* {{Release\|1=7.2\|2=\|3=[[Using your own Google OAuth client]] -- connecting to Google Sheets through your own Google Cloud registration}}		* {{Release\|1=7.2\|2=\|3=[[Using your own Google OAuth client]] -- connecting to Google Sheets through your own Google Cloud registration}}
			* {{Release\|1=7.2\|2=\|3=[[Using a Google service account]] -- opening a Google Sheet with no browser and nobody present}}
	* You can also use [[DbQuery\| ODBC]] -- a standard database access method to read from Excel spreadsheets.		* You can also use [[DbQuery\| ODBC]] -- a standard database access method to read from Excel spreadsheets.
	* [[SuppressExcelAlerts]]		* [[SuppressExcelAlerts]]

Using your own Google OAuth client

Lchrisman — Fri, 18 Sep 2026 15:45:17 GMT

ER 21588 Phase 4: shared Lumina registry key, GoogleOAuthScope, link to service accounts

Show changes

Using a Google service account

Lchrisman — Fri, 18 Sep 2026 15:45:16 GMT

ER 21588 Phase 4: opening a Google Sheet as a service account (SpreadsheetOpen account parameter)

New page

[[Category:Integration Functions]]
{{ReleaseBar}}

{{Release|1=7.2|2=|3=
Normally the [[Functions To Read Excel Worksheets#Backend|GoogleSheets backend]] opens a spreadsheet as ''you'': the first time, your web browser opens, you sign in to Google and choose the spreadsheet, and the connection is remembered on your computer.

That cannot work where there is nobody at a browser -- a server, a scheduled task, a build, a model running under [[Analytica Decision Engine|ADE]] on a machine nobody signs in to. For those, Analytica can open a spreadsheet as a Google '''service account''': an account that belongs to a program rather than a person, and that proves who it is with a key file instead of a sign-in. You share the spreadsheet with the service account's e-mail address, exactly as you would share it with a colleague, and pass its key to [[Functions To Read Excel Worksheets#SpreadsheetOpen|SpreadsheetOpen]] in the «account» parameter.

== When to use one ==

* An unattended machine: a scheduled model run, a server, a continuous-integration job, or ADE on a machine where nobody has ever run the desktop connect flow.
* A spreadsheet that should be read as ''itself'' rather than as whoever happens to run the model -- a reference dataset the model's author maintains, where you do not want every reader to need their own access to it.

Do '''not''' use one for an ordinary desktop model. There the browser connection is simpler, it keeps each person reading with their own permissions, and it needs no key to look after.

== Creating the service account ==

# In the [https://console.cloud.google.com/ Google Cloud console], choose or create a project, and enable the '''Google Drive API''' and the '''Google Sheets API''' for it. (The Picker API is not needed -- a service account never sees a file chooser.)
# Go to IAM and admin, '''Service accounts''', and create one. Give it a name you will recognize later. It needs no project roles: the only access that matters is the sharing you do in step 4.
# Open the new account, go to '''Keys''', '''Add key''', '''Create new key''', type '''JSON'''. Google downloads a small .json file, once -- it cannot be downloaded again. This file is the account's password; treat it like one.
# Copy the account's e-mail address, which looks like <code>something@''your-project''.iam.gserviceaccount.com</code>, and '''share each spreadsheet with it''' in Google Sheets exactly as you would with a person: Share, paste the address, Viewer for read-only or Editor if the model writes. A service account sees nothing that has not been shared with it.

The service account needs no consent screen, no Google verification, and no security assessment, because nobody is being asked to grant it anything: it holds its own credentials, and you decide what it can reach by sharing.

== Giving Analytica the key ==

Put the contents of the .json file in a [[Secret]], and pass the Secret as the «account» parameter:

:<code>SpreadsheetOpen("https://docs.google.com/spreadsheets/d/''id''/edit", account: Sheets_Robot_Key)</code>

where <code>Sheets_Robot_Key</code> is a Secret whose value is the whole JSON text. Set its '''Sinks''' to <code>SpreadsheetOpen</code> and its '''Destination''' to <code>https://oauth2.googleapis.com/</code>, so the key can be used for this and nothing else; Analytica refuses the substitution otherwise. Which storage kind the Secret uses -- in the model, an environment variable, per machine user, or a vault -- is your choice, and is the thing that decides who else can run the model.

Passing the JSON as a plain text literal works too, and is the wrong thing to do in a saved model: anyone who opens the file then has the key.

The «backend» parameter is not needed; a Google Sheets link selects the backend by itself.

== What is different with a service account ==

* '''Nothing interactive ever happens.''' No browser opens, no dialog appears, and nothing waits for a person. If the account cannot reach the spreadsheet the call reports that and stops.
* '''The file chooser is not involved.''' Any spreadsheet shared with the account opens directly from its link. There is no "pick one" mode, so <code>SpreadsheetOpen("")</code> and <code>showDialog: True</code> have nothing to offer.
* '''It ignores the desktop's connection entirely.''' The Windows user's own Google connection, and the [[Using your own Google OAuth client|client-registration settings]], play no part; the key carries its own identity and its own permissions. You can use a service account for one spreadsheet and your own connection for another in the same model.
* '''Reads and writes behave exactly as they do otherwise''': a snapshot on open, writes sent when the computation finishes, on <code>SpreadsheetSave(wb)</code>, or on <code>SpreadsheetSetInfo(wb, 'Refresh', true)</code>. Give the account '''Editor''' on the spreadsheet if the model writes to it.
* <code>SpreadsheetInfo(wb, 'Account')</code> reports the service account's address, so a model can say which identity a workbook was opened with.
* <code>SpreadsheetOpen("New", backend:'GoogleSheets', account: ''key'')</code> does work, but the new spreadsheet is created in the '''service account's own Drive''', where no person can see it. That is occasionally what you want for scratch space and almost never what you want otherwise; a service account has no Drive anyone can browse.

== When it does not work ==

The most common failure is the one that has nothing to do with Analytica: the spreadsheet was never shared with the service account. Analytica says so by name --

:''The Google service account ''name''@''project''.iam.gserviceaccount.com cannot open the spreadsheet ...''

-- and the cure is to share it at that address. Note that sharing a ''folder'' with the account shares what is in it, which is usually the tidier arrangement for a model that reads several spreadsheets.

A key that is damaged, truncated, or not a service-account key at all is reported when the call is evaluated, before any network request, so a mistyped Secret fails immediately rather than halfway through a run.

Some organizations' Workspace policies block service-account keys from being created at all, or disable them after a period. If the console will not produce a key, that is an administrator's setting, not a Google-wide limit.

=== Not supported ===

Domain-wide delegation -- a service account impersonating a member of your Workspace -- is not supported. The service account acts as itself, and sees what has been shared with it.
}}

== See Also ==

* [[Functions To Read Excel Worksheets]] -- [[Functions To Read Excel Worksheets#SpreadsheetOpen|SpreadsheetOpen]] and the [[Functions To Read Excel Worksheets#Backend|GoogleSheets backend]]
* [[Using your own Google OAuth client]]
* [[Secret]]
* [[Analytica Decision Engine]]

Analytica Command Line

Lchrisman — Fri, 18 Sep 2026 15:27:21 GMT

/eval: without a filename: ignored in 7.0, evaluated as of 7.1

← Older revision		Revision as of 15:27, 18 September 2026
Line 27:		Line 27:
	* <code>/rlm:''server''</code>: Specifies the server name (or port@serverName) that is running a Reprise License Manager with the desired centrally managed (e.g., floating) license.		* <code>/rlm:''server''</code>: Specifies the server name (or port@serverName) that is running a Reprise License Manager with the desired centrally managed (e.g., floating) license.

	* <code>/eval:''expression''</code>: (new to [[Analytica 6.0]]). Specifies an Analytica expression that is evaluated immediately after the model file that is specified on the command line finishes loading. The evaluating occurs after any proactively evaluated variables or buttons in the model. It does not dirty the model. The expression can include global variable assignments, and button identifiers. You will almost certainly want to include double quotes around the expression, and you need to escape any interior quotes by proceeding the quote with a backslash. The parameter is ignored if ''filename'' is not specified on the command line. See [[Running a model in a command line workflow]].		* <code>/eval:''expression''</code>: (new to [[Analytica 6.0]]). Specifies an Analytica expression that is evaluated immediately after the model file that is specified on the command line finishes loading. The evaluating occurs after any proactively evaluated variables or buttons in the model. It does not dirty the model. The expression can include global variable assignments, and button identifiers. You will almost certainly want to include double quotes around the expression, and you need to escape any interior quotes by proceeding the quote with a backslash. {{Release?\|1=7.1\|2=As of [[Analytica 7.1]], the expression is evaluated even when no ''filename'' appears on the command line; it then runs once the model that Analytica starts up with -- your startup model, or a new untitled model -- has finished loading.\|3=The parameter is ignored if ''filename'' is not specified on the command line.}} See [[Running a model in a command line workflow]].

	*: Example usage: <code>Analytica.exe /eval:"Claimant=\"JDoe\";Run_Batch;Exit" "Claim analysis.ana"</code>		*: Example usage: <code>Analytica.exe /eval:"Claimant=\"JDoe\";Run_Batch;Exit" "Claim analysis.ana"</code>

User Interface Typescript Commands

Lchrisman — Fri, 18 Sep 2026 15:02:32 GMT

ER 22199: this page has no {{ReleaseBar}}, so use the inline "new to" style instead of release gating

← Older revision		Revision as of 15:02, 18 September 2026
(One intermediate revision by the same user not shown)
Line 93:		Line 93:
	As with any typescript command, from a button [[OnClick]] event, this needs to be run as		As with any typescript command, from a button [[OnClick]] event, this needs to be run as
	:<code>[[EvaluateScript]]('Bye -')</code>		:<code>[[EvaluateScript]]('Bye -')</code>

			(new to [[Analytica 7.2]]) When your aim is to run a model from a command line and then exit, you no longer need <code>Bye</code> at all. The [[Analytica Command Line\|command line]] option <code>/evalThenExit:''expression''</code> evaluates ''expression'' and then exits without asking to save changes, so <code>EvaluateScript('Bye -')</code> no longer has to be tacked onto the end of the expression. See [[Running a model in a command line workflow]].

	==See Also==		==See Also==
	* [[Typescript]]		* [[Typescript]]
	* [[User interfaces]]		* [[User interfaces]]
			* [[Analytica Command Line]] -- including <code>/evalThenExit:</code>, which exits for you
			* [[Running a model in a command line workflow]]

What's new in Analytica 7.2?

Lchrisman — Fri, 18 Sep 2026 15:00:24 GMT

ER 22199: new /evalThenExit: command line option

← Older revision		Revision as of 15:00, 18 September 2026
Line 57:		Line 57:
	== New command line options ==		== New command line options ==
	See [[Analytica Command Line]].		See [[Analytica Command Line]].
			*; <code>/evalThenExit:«expression»</code>: Like <code>/eval:</code>, but Analytica exits as soon as «expression» has finished, without asking whether to save changes. It replaces the <code>/eval:"«expression»;EvaluateScript('Bye -')"</code> idiom that a [[Running a model in a command line workflow\|command line workflow]] used to need, and that was easy to forget.

	*; <code>/lib:«YourLib.ana»</code>: Loads an Analytica library into [[SysLib_Customizations]], which exists concurrently with your model (in a different [[Namespace]]). It survives across model closures, so it can appear as new built-in functionality. Useful for [[MCP server in Analytica\|MCP Servers]], QA testing, benchmarking, [[Running a model in a command line workflow\|batch processing]], GUI extensions, General (model-independent) [[Assista - Analytica AI Assistant/Custom user skills for Assista\|Custom Assista skill libraries]], etc.		*; <code>/lib:«YourLib.ana»</code>: Loads an Analytica library into [[SysLib_Customizations]], which exists concurrently with your model (in a different [[Namespace]]). It survives across model closures, so it can appear as new built-in functionality. Useful for [[MCP server in Analytica\|MCP Servers]], QA testing, benchmarking, [[Running a model in a command line workflow\|batch processing]], GUI extensions, General (model-independent) [[Assista - Analytica AI Assistant/Custom user skills for Assista\|Custom Assista skill libraries]], etc.

Running a model in a command line workflow

Lchrisman — Fri, 18 Sep 2026 15:00:24 GMT

ER 22199: new /evalThenExit: command line option

@@ Line 63: / Line 63: @@
 where ''expression'' and ''modelFile.ana'' are replaced as appropriate.
 === Launch the calculations of interest ===
@@ Line 77: / Line 83: @@
 === Exit the Analytica process ===
 After your calculation completes, you need to explicitly tell the process to terminate. This is accomplished by using the [[:Category:Typescript Commands|typescript command]] [[Bye]].

Analytica Command Line

Lchrisman — Fri, 18 Sep 2026 15:00:23 GMT

ER 22199: new /evalThenExit: command line option

← Older revision		Revision as of 15:00, 18 September 2026
Line 31:		Line 31:
	*: Example usage: <code>Analytica.exe /eval:"Claimant=\"JDoe\";Run_Batch;Exit" "Claim analysis.ana"</code>		*: Example usage: <code>Analytica.exe /eval:"Claimant=\"JDoe\";Run_Batch;Exit" "Claim analysis.ana"</code>
	*: In this example, <code>Claimant</code> is the identifier of an input variable in the model and <code>Run_batch</code> and <code>Exit</code> are names of a buttons in the model.		*: In this example, <code>Claimant</code> is the identifier of an input variable in the model and <code>Run_batch</code> and <code>Exit</code> are names of a buttons in the model.

			{{Release\|1=7.2\|2=\|3=
			* <code>/evalThenExit:''expression''</code>: (new to [[Analytica 7.2]]) The same as <code>/eval:</code>, except that Analytica exits as soon as ''expression'' has finished, without asking whether to save changes. This is almost always what you want in a [[Running a model in a command line workflow\|command line workflow]].
			*: Example usage: <code>Analytica.exe /evalThenExit:"Claimant=\"JDoe\";Run_Batch" "Claim analysis.ana"</code>
			*: Before 7.2, you had to write the exit into the expression yourself, as <code>/eval:"''expression'';EvaluateScript('[[User Interface Typescript Commands#Bye\|Bye]] -')"</code>. That was awkward and easy to leave out -- and when it was left out, the batch run did its work and then sat at an idle Analytica window forever, waiting for a person who was never coming.
			*: If ''expression'' exits on its own -- because it runs <code>Bye</code>, or presses a button that does -- that simply happens first, and this option then has nothing left to do.
			*: If ''expression'' fails, the error dialog still appears and waits to be dismissed before Analytica exits. Add <code>[[Analytica Command Line/Automation\|/Automation]]</code> when the run must not stop for a dialog under any circumstances.
			*: <code>/eval:</code> and <code>/evalThenExit:</code> may both appear on the same command line, in which case the <code>/eval:</code> expression is evaluated first.
			}}

	* <code>/comment:''text''</code>: (new to [[Analytica 6.0]]) The ''text'' is a comment that is ignored by Analytica. In one example usage, ACP3 adds a comment to each spawned processes to differentiate them in task manager.		* <code>/comment:''text''</code>: (new to [[Analytica 6.0]]) The ''text'' is a comment that is ignored by Analytica. In one example usage, ACP3 adds a comment to each spawned processes to differentiate them in task manager.

Functions To Read Excel Worksheets

Lchrisman — Fri, 18 Sep 2026 14:36:32 GMT

ER 21588: link to the new advanced page on using your own Google OAuth client

← Older revision		Revision as of 14:36, 18 September 2026
Line 56:		Line 56:
	*; Capabilities: Reads come from a snapshot taken when the workbook is opened. Writes made with [[SpreadsheetSetCell]] and [[SpreadsheetSetRange]], and sheets added or removed, are sent to Google when the computation finishes, when you call [[Functions_to_Write_Data_to_Excel_Worksheets#SpreadsheetSave\|SpreadsheetSave]](wb), or when the workbook is refreshed: <code>SpreadsheetSetInfo(wb, 'Refresh', true)</code> sends the pending writes and re-downloads the spreadsheet, so the values Google computed (and other people's edits) are seen. A native Google Sheet is exported by Google as an .xlsx snapshot (Google limits the export to 10 MB); an Excel workbook stored in Drive is downloaded as-is and written back as a whole file. The tab names the model sees (<code>SpreadsheetInfo(wb, 'Sheets')</code>, and «sheet» given by name) are the names in the exported snapshot, truncated to 31 characters, while writes are addressed to Google's real tab titles. <code>SpreadsheetOpen("New", backend:'GoogleSheets', title: "My sheet")</code> creates a new Google Sheet in your Drive. The second return value is the spreadsheet's link.		*; Capabilities: Reads come from a snapshot taken when the workbook is opened. Writes made with [[SpreadsheetSetCell]] and [[SpreadsheetSetRange]], and sheets added or removed, are sent to Google when the computation finishes, when you call [[Functions_to_Write_Data_to_Excel_Worksheets#SpreadsheetSave\|SpreadsheetSave]](wb), or when the workbook is refreshed: <code>SpreadsheetSetInfo(wb, 'Refresh', true)</code> sends the pending writes and re-downloads the spreadsheet, so the values Google computed (and other people's edits) are seen. A native Google Sheet is exported by Google as an .xlsx snapshot (Google limits the export to 10 MB); an Excel workbook stored in Drive is downloaded as-is and written back as a whole file. The tab names the model sees (<code>SpreadsheetInfo(wb, 'Sheets')</code>, and «sheet» given by name) are the names in the exported snapshot, truncated to 31 characters, while writes are addressed to Google's real tab titles. <code>SpreadsheetOpen("New", backend:'GoogleSheets', title: "My sheet")</code> creates a new Google Sheet in your Drive. The second return value is the spreadsheet's link.
	*; Return type: Returns a «GoogleSheetsWorkbook» object for a native Google Sheet, or a «LibXlWorkbook» object for an Excel file stored in Drive. <code>SpreadsheetInfo(wb, 'Backend')</code> returns <code>'GoogleSheets'</code> or <code>'LibXl'</code> accordingly, and <code>SpreadsheetInfo(wb, 'URL')</code> and <code>SpreadsheetInfo(wb, 'Account')</code> give its link and the Google account it was opened with.		*; Return type: Returns a «GoogleSheetsWorkbook» object for a native Google Sheet, or a «LibXlWorkbook» object for an Excel file stored in Drive. <code>SpreadsheetInfo(wb, 'Backend')</code> returns <code>'GoogleSheets'</code> or <code>'LibXl'</code> accordingly, and <code>SpreadsheetInfo(wb, 'URL')</code> and <code>SpreadsheetInfo(wb, 'Account')</code> give its link and the Google account it was opened with.
			*; Advanced: Analytica identifies itself to Google as an application registered by Lumina. An organization that would rather it identified itself as an application of their own -- because their Google Workspace administrator controls which outside applications may reach their data, for example -- can arrange that; see [[Using your own Google OAuth client]].
	}}		}}
	}}		}}
Line 424:		Line 425:
	* [[Excel spreadsheets read and write]]		* [[Excel spreadsheets read and write]]
	* [[Functions to Write Data to Excel Worksheets]] -- [[SpreadsheetSetCell]], [[SpreadsheetSetRange]] and [[SpreadsheetSave]]		* [[Functions to Write Data to Excel Worksheets]] -- [[SpreadsheetSetCell]], [[SpreadsheetSetRange]] and [[SpreadsheetSave]]
			* {{Release\|1=7.2\|2=\|3=[[Using your own Google OAuth client]] -- connecting to Google Sheets through your own Google Cloud registration}}
	* You can also use [[DbQuery\| ODBC]] -- a standard database access method to read from Excel spreadsheets.		* You can also use [[DbQuery\| ODBC]] -- a standard database access method to read from Excel spreadsheets.
	* [[SuppressExcelAlerts]]		* [[SuppressExcelAlerts]]

Running a model in a command line workflow

Lchrisman — Fri, 18 Sep 2026 14:35:08 GMT

Added release bar

← Older revision		Revision as of 14:35, 18 September 2026
Line 1:		Line 1:
	''Requires [[Analytica 6.0]] or later.''		''Requires [[Analytica 6.0]] or later.''

			{{ReleaseBar}}

	This page details how you can launch an Analytica model from a command line or batch file for the purpose of having it automatically run your model and exit, for example as part of an automated computational pipeline.		This page details how you can launch an Analytica model from a command line or batch file for the purpose of having it automatically run your model and exit, for example as part of an automated computational pipeline.

Using your own Google OAuth client

Lchrisman — Fri, 18 Sep 2026 14:34:25 GMT

Replace the wikitable with a definition list -- bare pipes broke the enclosing Release template

← Older revision		Revision as of 14:34, 18 September 2026
Line 49:		Line 49:
	for everyone on the computer. When a value appears in both, the HKEY_CURRENT_USER one wins. The key has no release number in it, so the setting applies to every installed Analytica release.		for everyone on the computer. When a value appears in both, the HKEY_CURRENT_USER one wins. The key has no release number in it, so the setting applies to every installed Analytica release.

	~~{\| class="wikitable"~~		;<code>GoogleOAuthClientId</code> (REG_SZ)
	~~! Value name !! Type !! Contents~~		:The full client ID, ending in <code>.apps.googleusercontent.com</code>
	\|-		;<code>GoogleOAuthClientSecret</code> (REG_SZ)
	\| <code>GoogleOAuthClientId</code> \|\| REG_SZ \|\| The full client ID, ending in <code>.apps.googleusercontent.com</code>		:The client secret
	\|-
	\| <code>GoogleOAuthClientSecret</code> \|\| REG_SZ \|\| The client secret
	\|}

	Set both. If the ID is given without the secret, Google refuses the connection. As a .reg file:		Set both. If the ID is given without the secret, Google refuses the connection. As a .reg file:

Using your own Google OAuth client

Lchrisman — Fri, 18 Sep 2026 14:32:28 GMT

ER 21588: advanced page -- registering your own Google OAuth client for the GoogleSheets backend

New page

[[Category:Integration Functions]]
{{ReleaseBar}}

{{Release|1=7.2|2=|3=
When the [[Functions To Read Excel Worksheets#Backend|GoogleSheets backend]] of [[Functions To Read Excel Worksheets#SpreadsheetOpen|SpreadsheetOpen]] connects to Google, Analytica identifies itself to Google as an application named '''Analytica''', registered by Lumina Decision Systems. That needs no setup and is the right arrangement for nearly everyone.

This page is for the few organizations that would rather have Analytica identify itself as an application registered by '''them'''. It describes what that does and does not change, when it is worth the trouble, and how to set it up.

== What the application identity is, and is not ==

The client ID and client secret that Analytica sends to Google say ''which program is asking''. They say nothing about ''who you are'', and nothing about ''which spreadsheets'' it may touch. In particular, using Lumina's registration does '''not''' restrict Analytica to non-confidential spreadsheets:

* Analytica asks Google for one permission, <code>drive.file</code>, which lets it see only the spreadsheets you yourself select in Google's file chooser, plus ones it creates. A confidential spreadsheet is no different from any other: select it in the chooser and Analytica can read and write it.
* No spreadsheet content and no Google credential ever passes through Lumina. Your browser talks to Google, your computer exchanges tokens with Google directly, and the resulting connection is kept in the Windows Credential Manager under your Windows account. Registering your own application changes none of that.
* Your own registration does not remove the browser step, and does not change which spreadsheets the chooser offers you.

== Why you might want your own ==

* '''Your organization controls which third-party applications may use its Google Workspace data.''' A Workspace administrator can allow or block individual applications (Admin console, under Security, API controls). If Analytica has not been allowed, connecting fails, or Google's chooser offers nothing you can select. An application registered inside your own organization is under your administrator's control from the start, instead of needing an exception made for an outside one.
* '''You want the consent screen, the grants and the audit trail inside your own organization.''' The browser names ''your'' application, the grants appear in your own Google Cloud project, and an administrator can review or revoke them centrally.
* '''You want your own API quota.''' Google counts Drive and Sheets API usage per Cloud project. Your own project gets its own quota, rather than sharing a pool with other Analytica users.
* '''You would rather Analytica's access to your data not depend on an application registered by another company at all.'''

If none of these apply to you, use the built-in registration and ignore this page.

== Registering the application with Google ==

You need a Google Cloud project, which is free.

# In the [https://console.cloud.google.com/ Google Cloud console], create a project, or choose one your organization already uses.
# Enable three APIs for it (APIs and services, then Enable APIs and services): '''Google Drive API''', '''Google Sheets API''' and '''Google Picker API'''. The Picker API is the one that presents the file chooser; without it the connection cannot finish.
# Configure the OAuth consent screen (Google Auth Platform, then Branding). Give it an application name -- this is the name the person sees in the browser, so use one they will recognize -- a user-support e-mail address, and a developer contact address.
#* Choose the '''Internal''' user type if your organization uses Google Workspace and only its own members need to connect. Internal applications skip Google's verification process entirely.
#* '''External''' also works. Because Analytica asks only for the non-sensitive <code>drive.file</code> permission, an External application can be published without a Google review. While it is left in ''Testing'', though, only the accounts listed as test users can connect, and their connections stop working after seven days.
# Create the credential: APIs and services, Credentials, Create credentials, '''OAuth client ID''', application type '''Desktop app'''. Copy the '''Client ID''' and the '''Client secret''' that Google shows. There is no redirect URI to fill in -- a desktop client may use the local loopback address that Analytica uses.

Google calls the second value a secret, but for a desktop application it is not a true secret: it is distributed inside the program, and Google's own documentation treats installed applications as unable to keep it confidential. Look after it as you would any configuration value, but it is not a password, and on its own it grants access to nothing.

== Telling Analytica to use it ==

Set two values in the registry, under

:<code>HKEY_CURRENT_USER\Software\Lumina Decision Systems\Analytica</code>

for one Windows user, or under

:<code>HKEY_LOCAL_MACHINE\SOFTWARE\Lumina Decision Systems\Analytica</code>

for everyone on the computer. When a value appears in both, the HKEY_CURRENT_USER one wins. The key has no release number in it, so the setting applies to every installed Analytica release.

{| class="wikitable"
! Value name !! Type !! Contents
|-
| <code>GoogleOAuthClientId</code> || REG_SZ || The full client ID, ending in <code>.apps.googleusercontent.com</code>
|-
| <code>GoogleOAuthClientSecret</code> || REG_SZ || The client secret
|}

Set both. If the ID is given without the secret, Google refuses the connection. As a .reg file:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Lumina Decision Systems\Analytica]
"GoogleOAuthClientId"="123456789012-examplexample.apps.googleusercontent.com"
"GoogleOAuthClientSecret"="GOCSPX-exampleexampleexample"

Removing both values restores the built-in registration.

The change takes effect at the next connection; there is no need to restart Analytica. Connections are remembered separately for each client ID, so the first spreadsheet you open after the change asks you to connect once more. Your earlier connection is left untouched, and is used again if you remove the two values.

== Checking that it worked, and disconnecting ==

Open any Google Sheets link with [[Functions To Read Excel Worksheets#SpreadsheetOpen|SpreadsheetOpen]]. The browser page that asks for permission should now name ''your'' application rather than Analytica. Afterwards:

:<code>SysLib_Internal::GoogleAccountEmail()</code> -- the Google account now connected, or Null when there is none.
:<code>SpreadsheetInfo(wb, 'Account')</code> -- the account an open workbook was opened with.

To disconnect -- which revokes the access at Google and forgets the stored connection -- evaluate

:<code>SysLib_Internal::DisconnectGoogleAccount()</code>

from a button's OnClick, or in the [[Typescript Window|Typescript window]]. It is a side effect, so it is refused inside a variable's Definition. It returns the e-mail address of the account that was disconnected, or Null when none was connected. You can also revoke Analytica's access at any time from [https://myaccount.google.com/permissions your Google account's permissions page].

== Notes and limits ==

* One Google connection is remembered at a time for a given client ID, for the Windows user who made it. [[Analytica Decision Engine|ADE]] scripts running as the same Windows user share that connection, which is why connecting once in Analytica is enough for them.
* Analytica asks for the <code>drive.file</code> permission with your registration exactly as it does with Lumina's. Registering your own application does not let it open spreadsheets that were never selected in the chooser.
* A model published to the [[Analytica Cloud Platform]] does not use these settings. There, each person connects their own Google account through the ACP server's own registration, and the settings on the author's computer play no part.
}}

== See Also ==

* [[Functions To Read Excel Worksheets]] -- [[Functions To Read Excel Worksheets#SpreadsheetOpen|SpreadsheetOpen]] and the [[Functions To Read Excel Worksheets#Backend|GoogleSheets backend]]
* [[Functions to Write Data to Excel Worksheets]]
* [[SpreadsheetInfo]]
* [[Analytica Cloud Platform]]

Functions To Read Excel Worksheets

Lchrisman — Fri, 18 Sep 2026 14:21:04 GMT

← Older revision		Revision as of 14:21, 18 September 2026
Line 1:		Line 1:
	[[Category:Excel to Analytica mappings]]		[[Category:Excel to Analytica mappings]]
			[[Category:Integration Functions]]

	__TOC__		__TOC__

Excel spreadsheets read and write

Lchrisman — Fri, 18 Sep 2026 14:20:32 GMT

← Older revision		Revision as of 14:20, 18 September 2026
Line 1:		Line 1:
	[[Category: Analytica User Guide]]		[[Category: Analytica User Guide]]
	[[Category:Excel to Analytica mappings]]		[[Category:Excel to Analytica mappings]]
			[[Category:Integration Functions]]

	<breadcrumbs> Analytica User Guide > Integration with data and applications > {{PAGENAME}}</breadcrumbs><br />		<breadcrumbs> Analytica User Guide > Integration with data and applications > {{PAGENAME}}</breadcrumbs><br />

Read and Write Spreadsheets

Lchrisman — Fri, 18 Sep 2026 14:20:06 GMT

← Older revision		Revision as of 14:20, 18 September 2026
Line 1:		Line 1:
	[[Category:Excel to Analytica mappings]]		[[Category:Excel to Analytica mappings]]
			[[Category:Integration Functions]]

	{{ReleaseBar}}		{{ReleaseBar}}
	__TOC__		__TOC__

Functions to Write Data to Excel Worksheets

Lchrisman — Fri, 18 Sep 2026 14:19:44 GMT

← Older revision		Revision as of 14:19, 18 September 2026
Line 1:		Line 1:
	[[Category:Excel to Analytica mappings]]		[[Category:Excel to Analytica mappings]]
			[[Category:Integration Functions]]

	__TOC__		__TOC__

Identifier

Lchrisman — Thu, 17 Sep 2026 23:17:05 GMT

ER 22398: identifier spelling is now a Preferences pulldown, not a hidden typescript setting

← Older revision		Revision as of 23:17, 17 September 2026
Line 97:		Line 97:
	{{Release\|6.4\|\| until you change it. You can increase it to allow for longer generated titles. It does not limit the length when you edit the <code>Identifier</code> attribute directly. Excessively lengthy identifiers can detract from expression readability, but you may find a larger length to be convenient.}}		{{Release\|6.4\|\| until you change it. You can increase it to allow for longer generated titles. It does not limit the length when you edit the <code>Identifier</code> attribute directly. Excessively lengthy identifiers can detract from expression readability, but you may find a larger length to be convenient.}}

	{{Release\|6.4\|\|There is an option to use backquoted titles (with spaces and punctuation) as the identifier instead of replacing disallowed characters with underscores, etc. This option is experimental and not exposed on the [[Preference Dialog]]. To try this, in typescript type:		{{Release\|6.4\|7.1\|There is an option to use backquoted titles (with spaces and punctuation) as the identifier instead of replacing disallowed characters with underscores, etc. This option is experimental and not exposed on the [[Preference Dialog]]. To try this, in typescript type:
	:<code>[[Naming]]:4</code>		:<code>[[Naming]]:4</code>
	Use 5 if you want it to ask first before changing the identifier.}}		Use 5 if you want it to ask first before changing the identifier.}}{{Release\|1=7.2\|2=\|3=How the identifier is spelled is a preference. An unlabeled pulldown in the '''Change identifier''' section of the [[Preference Dialog]] chooses between replacing disallowed characters with underscores (the default), three other underscore conventions, two camel-case conventions, and using the backquoted title exactly as you typed it -- so the title <code>"Annual Profit by Category"</code> can give <code>Annual_Profit_by_Category</code>, <code>annual_profit_by_category</code>, <code>AnnualProfitByCategory</code> or <code>`Annual Profit by Category`</code>, among others. See [[Preferences dialog]] for the full list, or [[System variables#Naming\|Naming]] to set it from an expression.}}

	== History ==		== History ==

System variables

Lchrisman — Thu, 17 Sep 2026 23:17:04 GMT

ER 22398: the identifier-spelling methods now in bits 2+ of Naming

← Older revision		Revision as of 23:17, 17 September 2026
Line 113:		Line 113:
	* 1 = Ask before changing the identifier. Do so only if the user agrees to change it.		* 1 = Ask before changing the identifier. Do so only if the user agrees to change it.
	* 2 = Automatically change the title without asking.		* 2 = Automatically change the title without asking.
	{{Release\|6.4\|\|		{{Release\|6.4\|7.1\|
	You can then add the method number to this value to determine which method is used:		You can then add the method number to this value to determine which method is used:
	* 0: Change invalid characters to underscores, e.g., The title <code>"Net Revenue"</code> results in the identifier <code>Net_Revenue</code>.		* 0: Change invalid characters to underscores, e.g., The title <code>"Net Revenue"</code> results in the identifier <code>Net_Revenue</code>.
	* 4: Use backquotes if there are invalid characters, e.g., The title <code>"Net Revenue"</code> results in the identifier <code>`Net Revenue`</code>.		* 4: Use backquotes if there are invalid characters, e.g., The title <code>"Net Revenue"</code> results in the identifier <code>`Net Revenue`</code>.
	}}		}}{{Release\|1=7.2\|2=\|3=You can then add a method number to this value to select how the identifier is spelled. Shown here for the title <code>"Annual Profit by Category"</code>:
			* 0: <code>Annual_Profit_by_Category</code> -- invalid characters become underscores, and each word keeps the capitalization it has in the title.
			* 4: <code>`Annual Profit by Category`</code> -- the title exactly, as a [[Identifier#Backquotes for arbitrary characters in an identifier\|backquoted identifier]].
			* 8: <code>Annual_Profit_By_Category</code> -- upper snake case.
			* 12: <code>annual_profit_by_category</code> -- lower snake case.
			* 16: <code>Annual_profit_by_category</code> -- sentence snake case.
			* 20: <code>AnnualProfitByCategory</code> -- upper camel case.
			* 24: <code>annualProfitByCategory</code> -- lower camel case.
			So a <code>Naming</code> of 22 means ''rename without asking, spelling the identifier <code>Annual_profit_by_category</code>''. Methods 0 and 4 predate the others, which is why 4 is out of numeric order. Methods 8 and 20 capitalize the first letter of each word and leave the rest of the word alone, so an acronym in the title survives -- <code>"NPV of cash flow"</code> gives <code>NPV_Of_Cash_Flow</code> -- while 12, 16 and 24 lower the whole identifier. A method number beyond this list is treated as method 0. You choose among these from an unlabeled pulldown in the '''Change identifier''' section of the [[Preferences dialog]].}}

	==== NameSize ====		==== NameSize ====

Preferences dialog

Lchrisman — Thu, 17 Sep 2026 23:17:04 GMT

ER 22398: identifier-spelling pulldown in Change identifier, + the 7.2 screenshot

← Older revision		Revision as of 23:17, 17 September 2026
Line 6:		Line 6:
	The '''Preferences '''dialog lets you inspect and set a variety of general preferences and styles. To open this''' '''dialog, select [[Preferences]] from the [[Edit menu]].		The '''Preferences '''dialog lets you inspect and set a variety of general preferences and styles. To open this''' '''dialog, select [[Preferences]] from the [[Edit menu]].

	:{{Release\|\|6.2\|[[File:Chapter4 34.png]]}}{{Release\|6.3\|6.3\|[[image:Preferences 6.3.png]]}}{{Release\|6.4\|\|[[image:Preferences 6.4.png]]}}		:{{Release\|\|6.2\|[[File:Chapter4 34.png]]}}{{Release\|6.3\|6.3\|[[image:Preferences 6.3.png]]}}{{Release\|6.4\|7.1\|[[image:Preferences 6.4.png]]}}{{Release\|7.2\|\|[[image:Preferences 7.2.png]]}}

	The easiest way to learn what each preference does is to move the mouse over it, and read the [[Tooltip]] (as in all dialog boxes). See below if you need more details.		The easiest way to learn what each preference does is to move the mouse over it, and read the [[Tooltip]] (as in all dialog boxes). See below if you need more details.
Line 13:		Line 13:

	===Change identifier===		===Change identifier===
	~~Normally~~, Analytica generates an identifier from the Title you give to each object, using ~~thefirst~~ 20 characters, and substituting '_' for any spaces or punctuation characters, (See [[Creating and editing nodes]] for more.)		By default, Analytica generates an identifier from the Title you give to each object, using the first 20 characters, and substituting '_' for any spaces or punctuation characters. (See [[Creating and editing nodes]] for more.)

	'''When title changes''': Check this box to change an object's [[identifier]] whenever you change its title. If not checked, it changes the identifier only when you explicitly edit it.		'''When title changes''': Check this box to change an object's [[identifier]] whenever you change its title. If not checked, it changes the identifier only when you explicitly edit it.

			{{Release\|1=7.2\|2=\|3='''Identifier spelling''' (the unlabeled pulldown): Selects how the identifier is spelled when Analytica derives it from a title. Each option is written in the convention it selects, so the list describes itself. Shown here for the title <code>Annual Profit by Category</code>:
			* <code>Same_case_as_title</code> (the default): <code>Annual_Profit_by_Category</code> -- spaces and punctuation become underscores, and each word keeps the capitalization it has in the title.
			* <code>Upper_Snake_Case</code>: <code>Annual_Profit_By_Category</code>
			* <code>lower_snake_case</code>: <code>annual_profit_by_category</code>
			* <code>Sentence_snake_case</code>: <code>Annual_profit_by_category</code>
			* <code>UpperCamelCase</code>: <code>AnnualProfitByCategory</code>
			* <code>lowerCamelCase</code>: <code>annualProfitByCategory</code>
			* <code>`Backquoted title`</code>: <code>`Annual Profit by Category`</code> -- keeps the title exactly, spaces and all, which is what requires the [[Identifier#Backquotes for arbitrary characters in an identifier\|backquotes]]. The '''characters''' limit above does not apply to this one.
			The two upper-case conventions capitalize the first letter of each word and leave the rest of the word alone, so an acronym in the title survives: <code>NPV of cash flow</code> gives <code>NPV_Of_Cash_Flow</code>, not <code>Npv_Of_Cash_Flow</code>. The lower-case and sentence-case conventions lower the whole identifier.

			The convention applies whenever Analytica derives an identifier from a title -- renaming an object whose title you changed, or naming a new one -- and [[Assista]] follows it for the objects she creates. It does not touch identifiers that already exist. It is saved with the model, in bits 2 and up of the [[System variables#Naming\|Naming]] system variable.}}

	'''Ask before renaming''': Check this box to see a confirmation dialog before it automatically changes any [[identifier]].		'''Ask before renaming''': Check this box to see a confirmation dialog before it automatically changes any [[identifier]].

What's new in Analytica 7.2?

Lchrisman — Thu, 17 Sep 2026 23:12:41 GMT

GUI

← Older revision		Revision as of 23:12, 17 September 2026
Line 29:		Line 29:
	* Added Drag-and-drop of selected text within and between textual attribute values. Formerly required Cut-Paste, but differs in that Drag-and-drop doesn't alter the clipboard.		* Added Drag-and-drop of selected text within and between textual attribute values. Formerly required Cut-Paste, but differs in that Drag-and-drop doesn't alter the clipboard.
	* The [[Preferences dialog]] exposes some new preference settings:		* The [[Preferences dialog]] exposes some new preference settings:
	** The method used when generating identifiers from titles.		** The method used when generating identifiers from titles. (Which Assista will also use when naming objects)
	** Whether display-only arrows should be show as dashed.		** Whether display-only arrows should be show as dashed.
	** The time zone used for new date-time values (such as when parsing dates).		** The time zone used for new date-time values (such as when parsing dates).

File:Preferences 7.2.png

Lchrisman — Thu, 17 Sep 2026 23:12:09 GMT

Lchrisman uploaded File:Preferences 7.2.png The Preferences dialog in Analytica 7.2, which adds the identifier-spelling pulldown to the '''Change identifier''' section, '''Display-only arrows drawn as dashed''', and '''Time zone'''.

New page

== Summary ==
The Preferences dialog in [[Analytica 7.2]], which adds the identifier-spelling pulldown to the '''Change identifier''' section, '''Display-only arrows drawn as dashed''', and '''Time zone'''.

Secret/Vault API

Lchrisman — Thu, 17 Sep 2026 21:56:20 GMT

ER 22434: vault-shared is operator-only and scoped to the account on ACP servers

← Older revision		Revision as of 21:56, 17 September 2026
Line 66:		Line 66:
	</pre>		</pre>

	Path segments are URL-encoded. <code>{identity}</code> is the session's user identity for <code>vault-user</code> secrets~~, and the literal~~ <code>-</code> ~~for~~ <code>~~vault~~-shared</code>. <code>{policyFp}</code> is the secret's policy fingerprint.		Path segments are URL-encoded. <code>{identity}</code> is the session's user identity for <code>vault-user</code> secrets. For <code>vault-shared</code> secrets it is <code>account:«account name»</code> when the model was opened from an account (subscription) folder on an Analytica Cloud Platform server -- shared secrets are scoped to the account, so two customers' models that declare the same secret with the same policy never share a value -- and the literal <code>-</code> for a model outside every account and on the desktop. <code>{policyFp}</code> is the secret's policy fingerprint.

	<pre>		<pre>
Line 85:		Line 85:
	* '''Failure is unavailability.''' Any other status, a TLS failure, or a timeout makes the secret cleanly unavailable (the resulting error names the vault alias). The engine never falls back to a different store.		* '''Failure is unavailability.''' Any other status, a TLS failure, or a timeout makes the secret cleanly unavailable (the resulting error names the vault alias). The engine never falls back to a different store.
	* The engine may cache a fetched value in process memory for the session (scrubbed on close). A 404 on a <code>vault-user</code> secret triggers the masked credential prompt in the client, and a successful set invalidates any cached miss. A 404 on a <code>vault-shared</code> secret is an ''operator'' error -- the session gets a clean failure, and no end user is ever prompted to supply a deployment-wide secret.		* The engine may cache a fetched value in process memory for the session (scrubbed on close). A 404 on a <code>vault-user</code> secret triggers the masked credential prompt in the client, and a successful set invalidates any cached miss. A 404 on a <code>vault-shared</code> secret is an ''operator'' error -- the session gets a clean failure, and no end user is ever prompted to supply a deployment-wide secret.
			* '''A model never writes a <code>vault-shared</code> secret.''' <code>Value of s := ...</code> and <code>:= Null</code> on a vault-shared declaration are errors from every context (model code, button scripts, typescript); the engine only ever <code>GET</code>s such a secret. Shared values are provisioned by a deployment operator directly in the vault, under the identity and fingerprint the vault's log shows for the model's request.

	== Signed identity assertions ==		== Signed identity assertions ==

Att ArrowProperties

Lchrisman — Thu, 17 Sep 2026 21:24:34 GMT

← Older revision		Revision as of 21:24, 17 September 2026
Line 40:		Line 40:
	#* 1 = A drawn arrow remains even when there is no true dependency.		#* 1 = A drawn arrow remains even when there is no true dependency.

	The displayDashStyle is used for drawn arrows that have no real dependency, but only when the dashStyle is not explicitly set. The main use case for this one is to change the model-wide default by changing it on the [[ArrowClass]] object if you don't like the default of showing these arrows as dashed, for example to restore the default prior to [[Analytica 6.3]] of showing display arrows the same as real arrows.		The displayDashStyle is used for drawn arrows that have no real dependency, but only when the dashStyle is not explicitly set. The main use case for this one is to change the model-wide default by changing it on the [[ArrowClass]] object if you don't like the default of showing these arrows as dashed, for example to restore the default prior to [[Analytica 6.3]] of showing display arrows the same as real arrows. Starting in [[Analytica 7.2]] you can toggle this from the [[Preferences dialog]].

	== See Also ==		== See Also ==

What's new in Analytica 7.2?

Lchrisman — Thu, 17 Sep 2026 20:57:35 GMT

21588 -- 'Backend' option to SpreadsheetInfo

← Older revision		Revision as of 20:57, 17 September 2026
(2 intermediate revisions by the same user not shown)
Line 28:		Line 28:
	* A user input node with a '''[List]''' control pops up a new list-editor dialog, similar to the one in ACP. Previously this opened the Object Window where you would edit the list. The new dialog focuses solely on the list without all the other attributes.		* A user input node with a '''[List]''' control pops up a new list-editor dialog, similar to the one in ACP. Previously this opened the Object Window where you would edit the list. The new dialog focuses solely on the list without all the other attributes.
	* Added Drag-and-drop of selected text within and between textual attribute values. Formerly required Cut-Paste, but differs in that Drag-and-drop doesn't alter the clipboard.		* Added Drag-and-drop of selected text within and between textual attribute values. Formerly required Cut-Paste, but differs in that Drag-and-drop doesn't alter the clipboard.
			* The [[Preferences dialog]] exposes some new preference settings:
			** The method used when generating identifiers from titles.
			** Whether display-only arrows should be show as dashed.
			** The time zone used for new date-time values (such as when parsing dates).

	== Built-in functions or structs ==		== Built-in functions or structs ==
	* The [[Functions To Read Excel Worksheets\|Spreadsheet functions]] now work directly with live Google sheets.		* The [[Functions To Read Excel Worksheets\|Spreadsheet functions]] now work directly with live Google sheets.
			* A new option to <code>[[SpreadsheetInfo]]( wb, 'Backend')</code>, to programatically detect which backend the workbook uses (<code>'LibXl'</code>, <code>'Excel'</code> or <code>'GoogleSheets'</code>).
	* [[FileExists]]( filepath'', files, folders'' ) tests whether a file or folder exists, without the [[FileSystemListing]] idiom that this used to require. Requires {{Analytica Developer}} or better.		* [[FileExists]]( filepath'', files, folders'' ) tests whether a file or folder exists, without the [[FileSystemListing]] idiom that this used to require. Requires {{Analytica Developer}} or better.
	* New parameters, «map» and «includeNull» added to [[Flatten]] (...). Makes it easy and efficient to concatenate a collection of lists when the lists are behind [[references]] or in [[Struct]] members.		* New parameters, «map» and «includeNull» added to [[Flatten]] (...). Makes it easy and efficient to concatenate a collection of lists when the lists are behind [[references]] or in [[Struct]] members.

Preferences dialog

Lchrisman — Thu, 17 Sep 2026 20:12:18 GMT

ER 21483: document the new "Display-only arrows drawn as dashed" preference (7.2)

← Older revision		Revision as of 20:12, 17 September 2026
Line 59:		Line 59:

	:[[File:Chapter4 38.png]]		:[[File:Chapter4 38.png]]

			{{Release\|7.2\|\|'''Display-only arrows drawn as dashed''': A ''display-only arrow'' is an arrow that is drawn between two nodes but does not correspond to an actual dependency -- the node at its head does not use the value of the node at its tail in its [[definition]]. When this is checked (the default since [[Analytica 6.3]]), display-only arrows are drawn dashed so that you can tell them apart from real dependency arrows; when it is unchecked they are drawn solid, like any other arrow. This is independent of '''Show undefined''' above, so you can have dashed display-only arrows without cross-hatching on undefined nodes, and vice versa. It sets the model-wide default only -- the dash style of an individual arrow, set from the '''Dash style''' item on that arrow's right-mouse menu, still takes precedence. Saved with the model, as the <code>displayDashStyle</code> field of the [[Att_ArrowProperties]] attribute of [[ArrowClass]].}}

	'''Show result mode icons: mid, µ±''': {{Assista\|key\|Show or hide SICN, mid-icon, uncertainty icon, dist icon}} Display a small icon to the right of a [[User output node]] to indicate which uncertainty view is selected.		'''Show result mode icons: mid, µ±''': {{Assista\|key\|Show or hide SICN, mid-icon, uncertainty icon, dist icon}} Display a small icon to the right of a [[User output node]] to indicate which uncertainty view is selected.

What's new in Analytica 7.2?

Lchrisman — Thu, 17 Sep 2026 19:07:33 GMT

Built-in functions or structs

← Older revision		Revision as of 19:07, 17 September 2026
(2 intermediate revisions by the same user not shown)
Line 30:		Line 30:

	== Built-in functions or structs ==		== Built-in functions or structs ==
			* The [[Functions To Read Excel Worksheets\|Spreadsheet functions]] now work directly with live Google sheets.
	* [[FileExists]]( filepath'', files, folders'' ) tests whether a file or folder exists, without the [[FileSystemListing]] idiom that this used to require. Requires {{Analytica Developer}} or better.		* [[FileExists]]( filepath'', files, folders'' ) tests whether a file or folder exists, without the [[FileSystemListing]] idiom that this used to require. Requires {{Analytica Developer}} or better.
	* New parameters, «map» and «includeNull» added to [[Flatten]] (...). Makes it easy and efficient to concatenate a collection of lists when the lists are behind [[references]] or in [[Struct]] members.		* New parameters, «map» and «includeNull» added to [[Flatten]] (...). Makes it easy and efficient to concatenate a collection of lists when the lists are behind [[references]] or in [[Struct]] members.
	* [[SortIndex]], [[Sort]] and [[Rank]] can now accept a «lessThat» function for custom comparisons. See [[Using an ordering function when sorting]].		* [[SortIndex]], [[Sort]] and [[Rank]] can now accept a «lessThat» function for custom comparisons. See [[Using an ordering function when sorting]].
			* A new optional «timeZone» parameter added to [[ParseDate]], [[ParseCSV]], [[NumberToText]], and [[Today]]. Controls which time zone a newly created date-time number (such as when parsed) is created in. [[ParseDate]] and [[ParseCSV]] now recognize ISO 8601 and RFC 3339 date-time format; These are used by many web services, and may include an explicit time zone, which gets converted into the active or specified time zone.
	* (Esoteric) A new parameter, «sensitive», to [[AskMsgText]] and [[MsgBox]]. Used with the new <code>/AutomationTrace</code> [[Analytica Command Line\|command line]] option to prevent sensitive info (like a credential or API key) from being logged.		* (Esoteric) A new parameter, «sensitive», to [[AskMsgText]] and [[MsgBox]]. Used with the new <code>/AutomationTrace</code> [[Analytica Command Line\|command line]] option to prevent sensitive info (like a credential or API key) from being logged.
	* (''Experimental'') New [[Timer]] struct for scheduling an evaluation.		* (''Experimental'') New [[Timer]] struct for scheduling an evaluation.
Line 39:		Line 41:
	* The [[UncertainLMH]] distribution now allows «xLow»=«lb» or «xHigh»=«ub». This means that 10% (or more generally «pLow») of the probability sits at the «lb» or «ub» value creating a discontinuity in the CDF (an infinite spike in the PDF) at that value.		* The [[UncertainLMH]] distribution now allows «xLow»=«lb» or «xHigh»=«ub». This means that 10% (or more generally «pLow») of the probability sits at the «lb» or «ub» value creating a discontinuity in the CDF (an infinite spike in the PDF) at that value.
	* Added an «asIndex» parameter to [[HandleFromIdentifier]]. The same already existed on [[Handle]]. Used to disambiguate in the case of a self-indexed array-valued variable.		* Added an «asIndex» parameter to [[HandleFromIdentifier]]. The same already existed on [[Handle]]. Used to disambiguate in the case of a self-indexed array-valued variable.
	* When <code>[[Area]](y,x)</code> or <code>[[Integrate]](y,x)]]</code> appear in a [[DefineOptimization]] formulation where <code>y</code> depends on decision variables, the analyzer recognizes this as a linear or quadratic relationship when deciding whether the problem is an «LP», «QP» or «NLP».		* When <code>[[Area]](y,x)</code> or <code>[[Integrate]](y,x)</code> appear in a [[DefineOptimization]] formulation where <code>y</code> depends on decision variables, the analyzer recognizes this as a linear or quadratic relationship when deciding whether the problem is an «LP», «QP» or «NLP».

	== Dates and time zones ==		== Dates and time zones ==

Functions To Read Excel Worksheets

Lchrisman — Thu, 17 Sep 2026 18:12:03 GMT

SpreadsheetOpen(filename, showDialog, title{{Release|7.0||, backend}})

← Older revision		Revision as of 18:12, 17 September 2026
Line 12:		Line 12:
	Opens a spreadsheet file and returns a workbook object for use by other functions (such as [[SpreadsheetCell]] or [[SpreadsheetRange]]) to read from or write to the file.		Opens a spreadsheet file and returns a workbook object for use by other functions (such as [[SpreadsheetCell]] or [[SpreadsheetRange]]) to read from or write to the file.

	The returned object displays in a result table as <code>«ExcelWorkbook»</code>{{Release\|7.0\|\| or <code>«LibXlWorkbook»</code>, depending on the «backend» used}}{{Release\|1=7.2\|2=\|3=~~; a~~ workbook opened from a native Google Sheet displays as <code>«GoogleSheetsWorkbook»</code> (an Excel file stored in Google Drive ~~still~~ displays as <code>«LibXlWorkbook»</code>)}}.		The returned object displays in a result table as <code>«ExcelWorkbook»</code>{{Release\|7.2\|\|, <code>«GoogleSheetsWorkbook»</code> }}{{Release\|7.0\|\| or <code>«LibXlWorkbook»</code>, depending on the «backend» used.}} {{Release\|1=7.2\|2=\|3=A workbook opened from a native Google Sheet displays as <code>«GoogleSheetsWorkbook»,</code> but an Excel file stored in Google Drive displays as <code>«LibXlWorkbook»</code>.}}

	Unless you include a complete file path in «filename», Analytica looks for the file in the [[CurrentDataFolder]]. You can also provide the name of a workbook that is currently open in Excel, even if it has not yet been saved to disk.		Unless you include a complete file path in «filename», Analytica looks for the file in the [[CurrentDataFolder]]. You can also provide the name of a workbook that is currently open in Excel, even if it has not yet been saved to disk.