File Directories and File Types on Client Machine

This topic discusses the file directory and file types found on the machine where Designer XI is installed.

IMPORTANT: There are two possible file directory paths. It depends on when you first installed the Designer XI application.

If you installed for the first time prior to the MSIX Migration (roughly June 2022), then the file directory starts with C:\Users\username\AppData\Local or C:\Users\username\AppData\Roaming.
If you installed for the first time after the MSIX Migration, then the file directory starts with C:\Users\username\AppData\Local\Packages\ArcFMDesigner_qybjwhg5w8jy8\LocalCache\Local or C:\Users\username\AppData\Local\Packages\ArcFMDesigner_qybjwhg5w8jy8\LocalCache\Roaming.

Install Directory

On the client machine, the install directory and the configuration file name vary based on whether the install date was before or after MSIX migration (see Important note above).

For Designer XI installation prior to the MSIX Migration (roughly June 2022), the install directory is C:\Users\[username]\AppData\Local\DesignerXI. Insert your username in the directory path, replacing [username]. The folder contains installation directories labeled by release number.

File	Description
SE.Geospatial.Electric.DesktopDesigner.exe	This is the application executable.
SE.Geospatial.Electric.DesktopDesigner.exe.config	This is a configuration file that includes advanced options

For Designer XI installation after the MSIX Migration, the install directory is C:\Program Files\WindowsApps\ArcFMDesigner_[version number]_x64__qybjwhg5w8jy8\SE.Geospatial.Electric.DesktopDesigner. Insert the version number of Designer XI on your machine, replacing [version number] in the directory path. Note the difference in the configuration file name.

File	Description
SE.Geospatial.Electric.DesktopDesigner.exe	This is the application executable.
SE.Geospatial.Electric.DesktopDesigner.dll.config	This is a configuration file that includes advanced options

NOTE: You can look in Windows Task Manager while running the Designer XI application to verify the install directory. If you don’t see the Command Line column on the Processes tab, you can right click in any column header and select Command Line to add it to your view.

Windows Task Manager screenshot with red square highlighting Designer XI process and command line.

The version number changes when you upgrade Designer XI. The version number can be found using either of the following methods:

Windows Settings > Apps > Installed Apps > ArcFM Designer > Advanced Options
Designer XI app > User Settings > About > AcrFM Designer XI. In this case the build number is the same as version number.

Client Log File (Designer.log)

On the client machine, the app log file, called Designer.log, is located in C:\Users\username\AppData\Local\Schneider_Electric\Designer or C:\Users\username\AppData\Local\Packages\ArcFMDesigner_qybjwhg5w8jy8\LocalCache\Local\Schneider_Electric\Designer

File	Description
Designer.log	This is a stream of log output from the Designer XI application. This includes notes on periodic maintenance, initialization notes, records of usages, and error logs.

AppData Directory

The AppData directory is located in C:\Users\username\AppData\Roaming\SE or C:\Users\username\AppData\Local\Packages\ArcFMDesigner_qybjwhg5w8jy8\LocalCache\Roaming\SE. That directory contains the following folders:

Folder	Description
Catalog	This contains data downloaded from the Catalog Service. This is information you see in Solution Center > Designer Plugin > Catalog > Equipment for the same tenant. The Catalog Service is defined in Solution Center > Tenancy Plugin > Service Discovery > Catalog field.
DesignerXI	This contains the offline cache of many auto-generated data files used by the application. For example, it contains eTags (tracking files to determine if the service has updates to download) and feature flags (offline cache of current feature flags enabled for the tenant).
Map Layout	This contains data downloaded from the Print Service and design print information. It also contains an offline cache of map note graphics.
Styles	This contains two file types: styles.json: This is the configuration of Design Styles for the tenant that was most recently downloaded when the application was last launched. It contains a list of ElectricStyles[] and DesignStyles[]. In each style array, you can find the individual configuration choices. [id].stlyx: In short, this is the Design Style file uploaded to the configuration. You can match the “id” in the .stylx name to the “id” found within the styles.json file.
Workflow	This contains data downloaded from the Catalog Service and dynamic design information. Read more below in the Workflow Directory in AppData section.

Workflow Directory in AppData

The Workflow directory contains the following files:

File	Description
[designuniqueID].dnx	This file has a small amount of metadata from the Design and Work Request resources from the Coordination Service. It is primarily the file that contains the “design.” As the design is modified, this file updates to represent the modifications, including all “playback” information required to revert changes and replay navigation choices. It also includes graphics and attributes pulled from the feature service. Finally, it also includes the initial feeder or DesignRegion extract when the work order/design is created.
[designuniqueID].dsr.json	This is similar to the .dnx file. However, as the design is modified, this file represents only the latest snapshot of the design and includes CU reference information.
[designuniqueID].etag	This is a tracking file to determine if the service has updates to download. See the topic Entity Tags (eTags) for more information.
CompatibleUnitData.json	This file contains data downloaded from the Catalog Service. This is information you see in Solution Center > Designer Plugin > Catalog > Compatible Unit for the same tenant.
MacroCompatibleUnitData.json	This file contains data downloaded from the Catalog Service. This is information you see in Solution Center > Designer Plugin > Catalog > Macro Compatible Unit for the same tenant.
SpecToCuRelationshipData.json	This file contains data downloaded from the Catalog Service. This is information you see in Solution Center > Designer Plugin > Catalog under Compatible Unit, Macro CU, or Equipment where you have defined a “Relationship” between a CU and Equipment specification.

Roaming\SE.Geospatial.DesktopDesigner Directory

The Roaming\SE.Geospatial.DesktopDesigner directory contains the following files:

File	Description
DeferUntilOnline.db	In this directory, the database name appears as DeferUntilOnline_<userId>_<tenantId>.db. This SQLite database stores a queue of commands executed when the user requests a design to be saved. This queue is used regardless of offline/online state and is processed every 1 minute. The following actions currently take advantage of the “defer until online” concept: Save print template Start assignment (if not already started) Update Work Request in Coordination Service Update Design in Coordination Service Save Design in Coordination Service Save DSR Storage Service

File

Description

DeferUntilOnline.db

In this directory, the database name appears as DeferUntilOnline_<userId>_<tenantId>.db.

This SQLite database stores a queue of commands executed when the user requests a design to be saved. This queue is used regardless of offline/online state and is processed every 1 minute. The following actions currently take advantage of the “defer until online” concept:

Save print template
Start assignment (if not already started)
Update Work Request in Coordination Service
Update Design in Coordination Service
Save Design in Coordination Service
Save DSR Storage Service

Logs for Other Services

Logs for on-premises services include:

On-Premises Service	Log Location
Storage Service	C:\inetpub\wwwroot\DesignStorage\logs
Polyfill Service	C:\inetpub\wwwroot\AGSPolyfill\logs