Importing Server Objects

Download Application Administrator Guide

You can import large numbers of server objects of several different types using text files that describe the items in a manner understandable by the server. This section lists the items you can import this way, the files required, and how those files must be constructed.

Items of the following types can be imported using the indicated files.

Preparing import files for attributes

To import multiple new attributes, you must create an item file that lists the basic parameters of each attribute on a separate line. Optionally, you can also use a description file to add descriptions in alternate languages to attributes.

Item file syntax

Create a new text file, and for each new attribute, on a separate line, include the following:

AttrClass{AttrName{AttrDesc{AttrType{AccessType{AttrDefault

where:

• AttrClass is the attribute class. Select one of the following:

  Field	Description
  SYSTEM	Describes the entire Longview system at the highest level. Attributes of this Attribute class specify systemwide characteristics. There is only one object in the SYSTEM Attribute class — the application itself.
  USER	Describes the Attributes of a particular user. Each user is an object in the USER Attribute class.
  SYMBOL	Describes the characteristics of individual symbols. Each symbol is an object in the SYMBOL Attribute class.

• AttrName is the name of the attribute to create.
• AttrDesc is a description for the attribute, in the default language of your application.
• AttrType is the type of attribute. Select one of the following:

  Field	Description
  DATE	Date and time.
  DATELIST	List of one or more Date values.
  DOUBLE	Numeric value.
  DOUBLELIST	List of one or more numeric values.
  INTEGER	Integer value.
  INTEGERLIST	List of one or more INTEGER values.
  STRING	Alphanumeric character string.
  STRINGLIST	List of one or more STRING values.
  SYMBOL	A valid symbol.
  SYMBOLLIST	List of one or more SYMBOL values.

• AccessType is the type of access to assign the attribute. Select one of the following:

  Field	Description
  READ	Read-only access, to allow the user to view the attribute value but not change it. This is the default. Symbol and System Attributes are always Read type.
  WRITE	Write access, to allow the user to set the attribute value. Write can be used only for User Attributes.

• AttrDefault is the default value for the attribute.

Description file syntax

The description file is used to add descriptions in alternate languages to attributes.

Create a new text file, and for each attribute and language, on a separate line, include the following:

AttrClass{AttrName{LanguageCode{TO{AttrDesc

where:

• AttrClass is the attribute class. Select one of the following:

  Field	Description
  SYSTEM	Describes the entire Longview system at the highest level. Attributes of this Attribute class specify system-wide characteristics. There is only one object in the SYSTEM Attribute class — the application itself.
  USER	Describes the Attributes of a particular user. Each user is an object in the USER Attribute class.
  SYMBOL	Describes the characteristics of individual symbols. Each symbol is an object in the SYMBOL Attribute class.

• AttrName is the name of the attribute to add the description for.
• LanguageCode is the two-letter language code of the language in which the description being added is written.
• AttrDesc is the alternate language description to assign to the attribute.

Preparing import files for attribute values

To create multiple new attribute values, you must create an item file that lists the basic parameters of each attribute value on a separate line.

Item file syntax

Create a new text file, and for each new attribute value, on a separate line, include the following:

AttrClass{AttrName{ObjectName{AttrValue

where:

• AttrClass is SYSTEM, USER, or SYMBOL.
• AttrName is the name of the attribute.
• ObjectName varies depending on the class:
  • SYSTEM — ObjectName is DBDEFAULT.
  • USER — ObjectName is the username.
  • SYMBOL — ObjectName is the symbol name.
• AttrValue is the attribute value.

Syntax example:

SYSTEM{SGPAccountsDimension{DBDEFAULT{Accounts

Preparing import files for journal entry sub-categories

To create multiple new journal entry sub-categories, you must create an item file that lists the basic parameters of each journal entry sub-category on a separate line.

Item file syntax

Create a new text file, and for each new journal entry sub-category, on a separate line, include the following:

Syntax example:

where:

• JESubCatDesc is the description for the sub-category.
• SchedName is optional and is the name of the schedule to which to associate the journal entry sub-category.
• RECLASSIFIED is used only when SchedName is specified, is optional, and allows base details to have different amounts than the total of the sub-details when the sub-category is applied. If this option is not used, base details are forced to equal the total of the sub-details.

Syntax example:

Preparing import files for server rules

To create multiple new rules, you must create an item file that lists the basic parameters of each rule on a separate line.

Item file syntax

Create a new text file, and for each new rule, on a separate line, include the following:

where:

• RuleID is a unique numeric rule ID used to assign to the rule.
• RuleType is MODEL, VALIDATION, ROLLUP, EVENT, or QUERY.
• RuleDefn is the statement that the system will evaluate when performing the server rule.
• Message is a message that is included with the rule. This field is valid for Validation rules and Event rules. For Validation it is the error message displayed when validation fails. For Event it is the body text of the email that is sent out when the rule is triggered.
• RuleDesc is a description for the rule.

Syntax Example:

Preparing import files for schedules

To create multiple new schedules, you must create an item file that lists the basic parameters of each schedule on a separate line.

Item file syntax (for standard or static schedules)

Create a new text file, and for each new schedule, on a separate line, include the following:

• For ExtraDimType = MIRROR

  DimName;ListofSymbols;Attr=Value

  LeafInclusion

  SortType

• For ExtraDimType = SIMPLE SYMBOL

  SymName1,SymName2,...

  SortType

• For ExtraDimType = NUMERIC

  StartRange,EndRange,Padding SortType

where:

• SchedName is a name for the schedule.
• SchedDesc is a description for the schedule.
• SchedType is STATIC, which permits data or text input to parent symbol intersections, or STANDARD for all other schedule dimensions.
• ListDims is a list of the dimensions that do not receive rollups. If there are no dimensions that do not receive rollups, use NONE.
• ExtraDimsNum is the number of extra dimensions this schedule will have.
• ExtraDimName is the name for the extra dimension.
• ExtraDimDesc is a description for the extra dimension.
• ExtraDimType is one of MIRROR, SIMPLE SYMBOL, or NUMERIC.
• DimName;ListofSymbols;Attr=Value is used only when ExtraDimType is MIRROR, and is the name of a dimension, a list of symbols delimited by commas, an attribute, and the value of that attribute. Attr=Value is optional and uses an attribute-based filter for the mirrored dimension.
• LeafInclusion is used only when ExtraDimType is MIRROR and is either TRUE or FALSE and indicates whether to include leaf symbols.
• SortType is one of UNSORTED, SORT_NAME, or SORT_DESC.
• SymName1,SymName2,. is the list of symbols to be used in a schedule where ExtraDimType is SIMPLE SYMBOL.
• StartRange is the value at the beginning of a range in a schedule where ExtraDimType is NUMERIC.
• EndRange is the value at the end of a range in a schedule where ExtraDimType is NUMERIC.
• Padding is either TRUE or FALSE and indicates whether decimal padding should be used.

Item file syntax (for intercompany schedules)

Create a new text file, and for each new schedule, on a separate line, include the following:

• For ExtraDimType = MIRROR

  DimName;ListofSymbols;Attr=Value

  LeafInclusion

  SortType

• For ExtraDimType = SIMPLE SYMBOL

  SymName1,SymName2,...

  SortType

• For ExtraDimType = NUMERIC

  StartRange,EndRange,Padding

  SortType

  OffsetFlag

  FixedDimFlag

  FixedDimSymName

where:

• SchedName is the name of the schedule.
• SchedDesc is the description of the schedule.
• SchedType is INTERCOMPANY.
• ListDims is a list of the dimensions that do not receive rollups.
• ExtraDimsNum is the number of extra dimensions this schedule will have.
• ExtraDimName is the name of an extra dimension.
• "ExtraDimDesc is the description of the extra dimension.
• ExtraDimType is one of MIRROR, SIMPLE SYMBOL, or NUMERIC.
• DimName;ListofSymbols;Attr=Value is used only when ExtraDimType is MIRROR, and is the name of a dimension, a list of symbols delimited by commas, an attribute, and the value of that attribute. Attr=Value is optional and uses an attribute-based filter for the mirrored dimension.
• LeafInclusion is used only when ExtraDimType is MIRROR and is either TRUE or FALSE and indicates whether to include leaf symbols.
• SortType is one of UNSORTED, SORT_NAME, or SORT_DESC.
• SymName1,SymName2,... is the list of symbols to be used in a schedule where ExtraDimType is SIMPLE SYMBOL.
• StartRange is the value at the beginning of a range in a schedule where ExtraDimType is NUMERIC.
• EndRange is the value at the end of a range in a schedule where ExtraDimType is NUMERIC.
• Padding is either TRUE or FALSE and indicates whether decimal padding should be used.
• OffsetFlag is either TRUE or FALSE and indicates whether this is an offset dimension.
• FixedDimFlag is either TRUE or FALSE and indicates whether there is a fixed dimension. This can be used only when OffsetFlag is FALSE for the extra dimension in an intercompany schedule.
• FixedDimSymName is the name of the fixed dimension symbol. This is used only when OffsetFlag is FALSE and FixedDimFlag is TRUE.

Syntax example: STANDARD MIRROR

Syntax example: INTERCOMPANY MIRROR dimension

Syntax example: INTERCOMPANY MIRROR dimension no offset

Syntax example: STANDARD NUMERIC dimension

Syntax example: STANDARD SIMPLE SYMBOL dimension

Description file syntax

The description file is used to add descriptions in alternate languages to schedules. The description file can also be used to add descriptions in alternate languages to extra dimensions.

Create a new text file, and for each new schedule, on a separate line, include the following:

where:

• SchedName is the name of the schedule.
• LanguageCode is the two-letter language code of the language in which the description being added is written.
• SchedDesc is the new alternate language description for the schedule.
• ExtraDimName is the name of an extra dimension.
• ExtraDimDesc is the description of the extra dimension.

Preparing import files for symbols

To create multiple new symbols, you must create an item file that lists the basic parameters of each symbol on a separate line.

Note: Using this process, you can create symbols for only one dimension at a time.

Item file syntax

Create a new text file, and for each new symbol, on a separate line, include the following:

SymName{SymDesc{SymType{ChildSort{BalanceType

where:

• SymName is a name for the symbol.
• SymDesc is the description for the symbol in the default language of your Longview system.
• SymType specifies the way the symbol should rolls up to its parent symbol. Possible types are:
  • STANDARD — Used when symbols add up normally.
  • CARRYFORWARD — ACCOUNTS and TIMEPER dimensions only; used for balance sheet and cash flow account symbols.
  • STATIC — Used when it does not make sense to total a hierarchy’s values.
• ChildSort specifies the way the symbols will be prioritized in the hierarchy. Possible values are:
  • 0 — When using a value of 0, the ChildSort option will be By Name (Ascending).
  • 1 — When using a value of 1, the ChildSort option will be By Name (Descending).
  • 2 — When using a value of 2, the ChildSort option will be Manually.
• BalanceType specifies the ACCOUNTS balance type. Possible values are:
  • DEBIT — Used for debit symbols.
  • CREDIT — Used for credit symbols.
  • NEITHER — Used if the symbol is neither credit nor debit.

Syntax example:

TESTACCOUNT{Test account description{STANDARD{2{CREDIT

Description file syntax

The description file is used to add descriptions in alternate languages to symbols.

Create a new text file, and for each new symbol, on a separate line, include the following:

SymName{DESCRIPTION{LanguageCode{TO{SymDesc

where:

• SymName is the name of the symbol.
• LanguageCode is the two-letter language code of the language in which the description being added is written.
• SymDesc is the new alternate language description for the symbol.

Syntax example:

TESTACCOUNT{DESCRIPTION{FR{TO{testing

Parent-child file syntax

Create a new text file, and for each symbol you want to automatically assign to a parent, on a separate line, include the following:

SymName{PARENT{NewParentSymName{Weight{Priority

where:

• SymName is the name of the symbol.
• NewParentSymName is the name of the symbol to which SymName is to be assigned.
• Weight is the mathematical effect of a child symbol on its parent symbol. Possible values are:
  • + (The symbol is added to its parent)
  • - (The symbol is subtracted from its parent)
  • 0 (The symbol has no mathematical effect on its parent)
• Priority is a number that designates a symbol's position in the hierarchy relative to its parent. Symbols are listed in order of ascending priority, with zeros falling at the bottom of the list. For more information, see “Priority”.

Syntax example:

TESTACCOUNT{PARENT{ACCOUNTPAR{+{0

Preparing import files for symbol access roles

To create multiple new symbol access roles, you must create an item file that lists the basic parameters of each symbol on a separate line.

Item file syntax

Create a new text file, and for each new symbol, on a separate line, include the following:

AccessType{DimName{SymName{SymAccess{NumLevels{Priority

where:

AccessType is any of:

• FULL — Write access to all symbols.
• FIXED — Access to only one symbol in the dimension.
• RESTRICTED — Select each symbol and level of access (read/write and levels).
• DimName is the dimension to which AccessType refers.
• SymName is the name of a symbol to which access is being granted. This is necessary only if AccessType is RESTRICTED or FIXED.
• SymAccess is either R (read) or W (write). This is necessary only if AccessType is RESTRICTED or FIXED.
• NumLevels is how many levels below this symbol in the hierarchy access is granted. This is necessary only if AccessType is RESTRICTED.
• Priority is a number greater than zero designating the precedence for the access type, where 1 is the highest priority and a priority of 0 gives precedence to any other non-zero value. This is necessary only if AccessType is RESTRICTED.

In addition, each role must be headed by the name of the role. The following is an example of an item file for creating symbol access roles (where “Analysis_Reporting_Access” and “Consolidation” are the names of the symbol access roles being created).

Analysis_Reporting_Access

Consolidation

Description file syntax

The description file is used to add descriptions in alternate languages to symbol access roles.

Create a new text file, and for each new symbol, on a separate line, include the following:

RoleName{LanguageCode{TO{RoleDesc

where:

• RoleName is the name of the symbol access role.
• LanguageCode is the two-letter language code of the language in which the description being added is written.
• RoleDesc is the new alternate language description of the symbol access role.

Preparing import files for users

Note: This section does not apply to systems that are on the ISW platform.

To create multiple new users, you must create an item file that lists the basic parameters of each user on a separate line. Exactly which parameters must be specified depends on whether you are creating Longview authenticated users, Windows authenticated users, or third-party web authenticated users. You can also create a parent-child file that will tell the application which user should belong to which group.

Note: For the optional fields (Email, HomePhone, and OfficePhone), if you do not enter a value, you must enter delimiters ( { ) for each empty field.

Item file syntax (Longview authenticated users)

Create a new text file, and for each new user, on a separate line, include the following:

UserName{LONGVIEW{UserDesc{Password{FirstName{LastName{Email{HomePhone{OfficePhone

where:

• UserName is the name of the user being created.
• LONGVIEW is a keyword designating the authentication type.
• UserDesc is a description of the user, written in the default language of your system.
• Password is the string the user must enter to authenticate.
• FirstName is the first name of the user.
• LastName is the last name of the user.
• Email is the email address at which the user can be contacted. This field is optional.
• HomePhone is the home phone number of the user. This field is optional.
• OfficePhone is the office phone number of the user. This field is optional.

Syntax example: Longview authentication

Item file syntax (Windows authenticated users)

Create a new text file, and for each new user, on a separate line, include the following:

UserName{WINDOWS{UserDesc{FirstName{LastName{Email{HomePhone{OfficePhone

where:

• UserName is the name of the user being created.

  Note: For Windows authenticated users, UserName must be in the following format: domain\UserID.

• WINDOWS is a keyword designating the authentication type.
• UserDesc is a description of the user, written in the default language of your system.
• FirstName is the first name of the user.
• LastName is the last name of the user.
• Email is the email address at which the user can be contacted. This field is optional.
• HomePhone is the home phone number of the user. This field is optional.
• OfficePhone is the office phone number of the user. This field is optional.

Item file syntax (third-party web authenticated users)

Create a new text file, and for each new user, on a separate line, include the following:

UserName{EXTERNAL{UserDesc{FirstName{LastName{Email{HomePhone{OfficePhone

where:

• UserName is the name of the user being created.
• EXTERNAL is a keyword designating the authentication type.
• UserDesc is a description of the user, written in the default language of your system.
• FirstName is the first name of the user.
• LastName is the last name of the user.
• Email is the email address at which the user can be contacted. This field is optional.
• HomePhone is the home phone number of the user. This field is optional.
• OfficePhone is the office phone number of the user. This field is optional.

Group membership file syntax

Create a new text file, and for each user you want to automatically assign to a group, on a separate line, include the following:

GroupName{UserName

where:

• GroupName is the name of the group.
• UserName is the name of the user to be added to the group.

Preparing import files for user authorizations

To set the authorizations for several users at the same time, you must create an item file that lists the authorizations for users, each parameter on a separate line. In this fashion, you can set as many parameters for as many users as you like.

Note: For systems on the ISW platform, if the user belongs to a group with authorizations configured, these user authorizations are ignored and the group authorizations apply instead.

Item file syntax

Create a new text file, and for each authorization granted to a particular user, include the following:

USER{UserName{OperationName{ObjectType{ObjectName

where:

• UserName is the name of the user to whom the authorization is being granted.
• OperationName is the name of an operation as it is in the database. The Authorization Operations are as follows:

Value	Description	Platform License
ADDINFOROFFICE	Access the Longview Add-In for Office. Note: You must also assign the CONNECTVIAAPPLICATIONFRAMEWORK authorization to allow users or user groups to access the Longview Add-In for Office.	Designer Power User Viewer
ADDINFOROFFICE SUBMITDATA	Submit data in the Longview Add-In for Office.	Designer Power User
ANALYSISREPORTING AUTHOR	Access Longview Analysis and Reporting as a Report Author.	Power user
ANALYSISREPORTING PUBLISHER	Access Longview Analysis and Reporting as a Report Publisher.	Designer
ANALYSISREPORTING USER	Access Longview Analysis and Reporting as a Report User.	Viewer
APPLICATION ADMINISTRATOR	Access Longview Application Administrator.	Admin Designer Service
ATTRIBUTE	Manage attributes.	Designer
BATCH	Manage batches.	Admin Designer
CONNECTVIA APPLICATION FRAMEWORK	Connect to the server using Longview Application Framework. Note: You must assign this authorization to allow users or user groups to access Longview Apps, Longview Designer, Longview tools and editors, the Longview Add-In for Office, and Longview Tax.	Admin Designer Power User Viewer Service
DASHBOARDDESIGNER	Access Longview Dashboard Designer.	Designer
DELETECOMMENTS	Delete any existing comments in the Data Server. Users without Delete Comments authorization can delete only their own comments before they are submitted to the database. Note: Delete existing comments functionality is available in Data Grids only.	Designer
DESIGNER	Access Longview Designer. Note: You must also assign the CONNECTVIAAPPLICATIONFRAMEWORK authorization to allow users or user groups to access Longview Designer.	Designer
DESIGNERDATA IMPORTSCREATE	Create data import apps in Longview Designer. Note: You must also assign the DESIGNER authorization to allow users or user groups to access Longview Designer.	Designer
DESIGNERDATA IMPORTSDELETE	Delete data import apps in Longview Designer. Note: You must also assign the DESIGNER authorization to allow users or user groups to access Longview Designer.	Designer
DESIGNERDATA IMPORTSMODIFY	Edit data import apps in Longview Designer. Note: You must also assign the DESIGNER authorization to allow users or user groups to access Longview Designer.	Designer
DESIGNERDATA IMPORTSPUBLISH	Publish data import apps in Longview Designer. Note: You must also assign the DESIGNER authorization to allow users or user groups to access Longview Designer.	Designer
DESIGNERLONGVIEW APPSPUBLISH	Publish Longview Apps in Longview Designer. Note: You must also assign the DESIGNER authorization to allow users or user groups to access Longview Designer.	Designer
FOREIGNEXCHANGE SETTINGS	Manage foreign exchange settings.	Admin Designer
GROUPADMINISTRATION	Perform group administration.	Does not apply
GROUPSYMBOLACCESS	Manage symbol access for groups.	Does not apply
INTERCOMPANYSETTINGS	Manage intercompany settings.	Designer
JOURNALENTRIES	Access Longview Journal Entries.	Designer Power User
JOURNALENTRY	Manage journal entries.	Designer Power User Service
JOURNALENTRYCURRENT PERIODCREATE	Create current period journal entries.	Designer Power User Service
JOURNALENTRYCURRENT PERIODPERMPOST	Permanently post current period journal entries.	Designer Power User Service
JOURNALENTRYCURRENT PERIODREVIEWPOST	Review post current period journal entries.	Designer Power User Service
JOURNALENTRYDELETE	Delete non-shared journal entries.	Designer Power User Service
JOURNALENTRYFUTURE PERIODCREATE	Create future period journal entries.	Designer Power User Service
JOURNALENTRYFUTURE PERIODPERMPOST	Permanently post future period journal entries.	Designer Power User Service
JOURNALENTRYFUTURE PERIODREVIEWPOST	Review post future period journal entries.	Designer Power User Service
JOURNALENTRYOWN PERMPOST	Permanently post own journal entries.	Designer Power User Service
JOURNALENTRYOWN REVIEWPOST	Review post own journal entries.	Designer Power User Service
JOURNALENTRYPRIOR PERIODADJCREATE	Create prior period journal entries.	Designer Power User Service
JOURNALENTRYPRIOR PERIODADJPERMPOST	Permanently post prior period journal entries.	Designer Power User Service
JOURNALENTRYPRIOR PERIODADJREVIEWPOST	Review post prior period journal entries.	Designer Power User Service
JOURNALENTRYRE STATEMENTCREATE	Create restatement journal entries.	Designer Power User Service
JOURNALENTRYRE STATEMENTPERMPOST	Permanently post restatement journal entries.	Designer Power User Service
JOURNALENTRYRE STATEMENTREVIEWPOST	Review post restatement journal entries.	Designer Power User Service
LOCK	Manage locks.	Designer Service
MAPPINGSEDITOR	Access the Mappings editor. Note: You must also assign the CONNECTVIAAPPLICATIONFRAMEWORK authorization to allow users or user groups to access the Mappings editor.	Designer Power User Service
MAPPINGSMANAGE	Create, modify, delete mappings. Note: You must also assign the MAPPINGSEDITOR authorization to allow users or user groups to access the Mappings editor.	Designer Power User Service
MAPSMANAGE	Create, modify, delete maps. Note: You must also assign the MAPPINGSEDITOR authorization to allow users or user groups to access the Mappings editor.	Designer Power User Service
MODIFYDATA	Submit data.	Designer Power User Service
NDDSETTINGS	Manage NDD settings.	Designer
ROLE	Manage symbol access roles.	Designer Service
RULE	Manage rules.	Designer Service
SCHEDULE	Manage schedules.	Designer Service
SERVERMANAGER	Access Longview Server Manager.	Admin Service Designer
SERVERMANAGERSTART	Start/stop the Longview server.	Admin Service Designer
SERVICEACCOUNTUSER ADMINISTRATOR	Sets the user to be a User Administrator.	Service
SERVICEACCOUNTRESTAPI	Sets user to be a Service Account User. Note: Can only be set using PUSER or a user who has User Administrator Authorization.	Admin Designer Service
SYMBOL	Manage symbols.	Designer Service
SYMBOLASSIGN	Assign symbols to a hierarchy. Must be used with SYMBOL.	Designer Service
SYMBOLATTRIBUTECREATE	Create symbol attributes. Must be used with ATTRIBUTE.	Designer Service
SYMBOLATTRIBUTEDELETE	Delete symbol attributes. Must be used with ATTRIBUTE.	Designer Service
SYMBOLATTRIBUTEMODIFY	Modify symbol attributes. Must be used with ATTRIBUTE.	Designer Service
SYMBOLCANCREATEROOT	Create root symbols. Must be used with SYMBOL, CREATESYMBOL.	Designer Service
SYMBOLCANDELETEROOT	Delete root symbols. Must be used with SYMBOL, SYMBOLDELETE.	Designer Service
SYMBOLCREATE	Create symbols. Must be used with SYMBOL.	Designer Service
SYMBOLDELETE	Delete symbols. Must be used with SYMBOL.	Designer Service
SYMBOLREMOVE	Remove symbols from a hierarchy. Must be used with SYMBOL.	Designer Service
SYMBOLSET	Modify symbols. Must be used with SYMBOL.	Designer Service
SYMBOLSWITCH	Switch symbols in a hierarchy. Must be used with SYMBOL.	Designer Service
SYSTEMATTRIBUTECREATE	Create system attributes. Must be used with ATTRIBUTE.	Designer Service
SYSTEMATTRIBUTEDELETE	Delete system attributes. Must be used with ATTRIBUTE.	Designer Service
SYSTEMATTRIBUTEMODIFY	Modify system attributes. Must be used with ATTRIBUTE.	Designer Service
USERADMINISTRATION	Perform user administration	Does not apply
USERATTRIBUTECREATE	Create user attributes. Must be used with ATTRIBUTE.	Designer Service
USERATTRIBUTEDELETE	Delete user attributes. Must be used with ATTRIBUTE.	Designer Service
USERATTRIBUTEMODIFY	Modify user attributes. Must be used with ATTRIBUTE.	Designer Service
USERRESETPASSWORD	Reset passwords.	Does not apply
USERSYMBOLACCESS	Manage symbol access for users.	Does not apply
VIEWDATA	View data.	Designer Power User Viewer Service
WORKFLOWDESIGNER	Access Longview Workflow Designer.	Designer

• ObjectType is GROUP and is used only when OperationName is USERADMINISTRATION or USERRESETPASSWORD.
• ObjectName is the group which the authorization specified for OperationName is applied to. ObjectName is used only when OperationName is USERADMINISTRATION or USERRESETPASSWORD.

Note: If ObjectName is AllUsers, the specified authorization is granted to the user for all users in the system.
For more information, see Understanding the AllUsers Group.

Syntax examples:

Preparing import files for group symbol access

To set the symbol access for several users at the same time, you must create an item file that lists the symbol access for users, each parameter on a separate line. In this fashion, you can set as many parameters for as many users as you like.

Item file syntax

Create a new text file, and for each symbol authorization granted to a particular user, include the following:

GROUP{GroupName{SymAccessRole{Dim-Name{Inherit{SymName{Access{NumLevels{Priority

where:

• GroupName is the name of the group to whom the access is being granted.
• SymAccessRole is the name of the symbol access role in which the symbol access being granted resides.
• DimName is the dimension to which Access refers.
• Inherit indicates whether the access is inherited from the symbol access role itself and is either TRUE or FALSE.
• SymName is the name of a symbol to which access is being granted. This needs to be set only if inherit is set to FALSE.
• Access is either R (read) or W (write). This needs to be set only if inherit is set to FALSE.
• NumLevels is how many levels below this symbol in the hierarchy access is granted. This needs to be set only if inherit is set to FALSE.
• Priority is a number greater than zero designating the precedence for the access type, where 1 is the highest priority and a priority of 0 gives precedence to any other non-zero value. This needs to be set only if inherit is set to FALSE.

Syntax examples:

Preparing import files for groups

To create multiple new groups, you must create an item file that lists the basic parameters of each group on a separate line.

Item file syntax

Create a new text file, and for each new group, on a separate line, include the following:

GroupName{GroupDesc

where:

• GroupName is the name of the group being created.
• GroupDesc is a description of the group, written in the default language of your system.

Group membership file syntax

Create a new text file, and for each user you want to automatically assign to a group, on a separate line, include the following:

GroupName{UserName

where:

• GroupName is the name of the group.
• UserName is the name of the user to be added to the group.

Preparing import files for group authorizations

Note: This section does not apply to systems that are on the ISW platform.

To set the authorizations for several groups at the same time, you must create an item file that lists the authorizations for groups, each parameter on a separate line. In this fashion, you can set as many parameters for as many groups as you like.

Note: For systems on the ISW Platform, when a user belongs to a group with authorizations configured, the group authorizations apply and the user's individual authorizations are ignored. If the group has no authorizations configured, the user's individual authorizations are used instead. Any group authorizations that exceed what the user's license permits are also ignored.

Item file syntax

Create a new text file, and for each authorization granted to a particular group, include the following:

GROUP{GroupName{OperationName{ObjectType{ObjectName where:

• GroupName is the name of the group to whom the authorization is being granted.
• OperationName is the name of an operation as it is in the database. The Authorization Operations are as follows:

Value	Description	Platform License
ADDINFOROFFICE	Access the Longview Add-In for Office. Note: You must also assign the CONNECTVIAAPPLICATIONFRAMEWORK authorization to allow users or user groups to access the Longview Add-In for Office.	Designer Power User Viewer
ADDINFOROFFICE SUBMITDATA	Submit data in the Longview Add-In for Office.	Designer Power User
ANALYSISREPORTING AUTHOR	Access Longview Analysis and Reporting as a Report Author.	Power user
ANALYSISREPORTING PUBLISHER	Access Longview Analysis and Reporting as a Report Publisher.	Designer
ANALYSISREPORTING USER	Access Longview Analysis and Reporting as a Report User.	Viewer
APPLICATION ADMINISTRATOR	Access Longview Application Administrator.	Admin Designer Service
ATTRIBUTE	Manage attributes.	Designer
BATCH	Manage batches.	Admin Designer
CONNECTVIA APPLICATION FRAMEWORK	Connect to the server using Longview Application Framework. Note: You must assign this authorization to allow users or user groups to access Longview Apps, Longview Designer, Longview tools and editors, the Longview Add-In for Office, and Longview Tax.	Admin Designer Power User Viewer Service
DASHBOARDDESIGNER	Access Longview Dashboard Designer.	Designer
DELETECOMMENTS	Delete any existing comments in the Data Server. Users without Delete Comments authorization can delete only their own comments before they are submitted to the database. Note: Delete existing comments functionality is available in Data Grids only.	Designer
DESIGNER	Access Longview Designer. Note: You must also assign the CONNECTVIAAPPLICATIONFRAMEWORK authorization to allow users or user groups to access Longview Designer.	Designer
DESIGNERDATA IMPORTSCREATE	Create data import apps in Longview Designer. Note: You must also assign the DESIGNER authorization to allow users or user groups to access Longview Designer.	Designer
DESIGNERDATA IMPORTSDELETE	Delete data import apps in Longview Designer. Note: You must also assign the DESIGNER authorization to allow users or user groups to access Longview Designer.	Designer
DESIGNERDATA IMPORTSMODIFY	Edit data import apps in Longview Designer. Note: You must also assign the DESIGNER authorization to allow users or user groups to access Longview Designer.	Designer
DESIGNERDATA IMPORTSPUBLISH	Publish data import apps in Longview Designer. Note: You must also assign the DESIGNER authorization to allow users or user groups to access Longview Designer.	Designer
DESIGNERLONGVIEW APPSPUBLISH	Publish Longview Apps in Longview Designer. Note: You must also assign the DESIGNER authorization to allow users or user groups to access Longview Designer.	Designer
FOREIGNEXCHANGE SETTINGS	Manage foreign exchange settings.	Admin Designer
GROUPADMINISTRATION	Perform group administration.	Does not apply
GROUPSYMBOLACCESS	Manage symbol access for groups.	Does not apply
INTERCOMPANYSETTINGS	Manage intercompany settings.	Designer
JOURNALENTRIES	Access Longview Journal Entries.	Designer Power User
JOURNALENTRY	Manage journal entries.	Designer Power User Service
JOURNALENTRYCURRENT PERIODCREATE	Create current period journal entries.	Designer Power User Service
JOURNALENTRYCURRENT PERIODPERMPOST	Permanently post current period journal entries.	Designer Power User Service
JOURNALENTRYCURRENT PERIODREVIEWPOST	Review post current period journal entries.	Designer Power User Service
JOURNALENTRYDELETE	Delete non-shared journal entries.	Designer Power User Service
JOURNALENTRYFUTURE PERIODCREATE	Create future period journal entries.	Designer Power User Service
JOURNALENTRYFUTURE PERIODPERMPOST	Permanently post future period journal entries.	Designer Power User Service
JOURNALENTRYFUTURE PERIODREVIEWPOST	Review post future period journal entries.	Designer Power User Service
JOURNALENTRYOWN PERMPOST	Permanently post own journal entries.	Designer Power User Service
JOURNALENTRYOWN REVIEWPOST	Review post own journal entries.	Designer Power User Service
JOURNALENTRYPRIOR PERIODADJCREATE	Create prior period journal entries.	Designer Power User Service
JOURNALENTRYPRIOR PERIODADJPERMPOST	Permanently post prior period journal entries.	Designer Power User Service
JOURNALENTRYPRIOR PERIODADJREVIEWPOST	Review post prior period journal entries.	Designer Power User Service
JOURNALENTRYRE STATEMENTCREATE	Create restatement journal entries.	Designer Power User Service
JOURNALENTRYRE STATEMENTPERMPOST	Permanently post restatement journal entries.	Designer Power User Service
JOURNALENTRYRE STATEMENTREVIEWPOST	Review post restatement journal entries.	Designer Power User Service
LOCK	Manage locks.	Designer Service
MAPPINGSEDITOR	Access the Mappings editor. Note: You must also assign the CONNECTVIAAPPLICATIONFRAMEWORK authorization to allow users or user groups to access the Mappings editor.	Designer Power User Service
MAPPINGSMANAGE	Create, modify, delete mappings. Note: You must also assign the MAPPINGSEDITOR authorization to allow users or user groups to access the Mappings editor.	Designer Power User Service
MAPSMANAGE	Create, modify, delete maps. Note: You must also assign the MAPPINGSEDITOR authorization to allow users or user groups to access the Mappings editor.	Designer Power User Service
MODIFYDATA	Submit data.	Designer Power User Service
NDDSETTINGS	Manage NDD settings.	Designer
ROLE	Manage symbol access roles.	Designer Service
RULE	Manage rules.	Designer Service
SCHEDULE	Manage schedules.	Designer Service
SERVERMANAGER	Access Longview Server Manager.	Admin Service Designer
SERVERMANAGERSTART	Start/stop the Longview server.	Admin Service Designer
SERVICEACCOUNTUSER ADMINISTRATOR	Sets the user to be a User Administrator.	Service
SERVICEACCOUNTRESTAPI	Sets user to be a Service Account User. Note: Can only be set using PUSER or a user who has User Administrator Authorization.	Admin Designer Service
SYMBOL	Manage symbols.	Designer Service
SYMBOLASSIGN	Assign symbols to a hierarchy. Must be used with SYMBOL.	Designer Service
SYMBOLATTRIBUTECREATE	Create symbol attributes. Must be used with ATTRIBUTE.	Designer Service
SYMBOLATTRIBUTEDELETE	Delete symbol attributes. Must be used with ATTRIBUTE.	Designer Service
SYMBOLATTRIBUTEMODIFY	Modify symbol attributes. Must be used with ATTRIBUTE.	Designer Service
SYMBOLCANCREATEROOT	Create root symbols. Must be used with SYMBOL, CREATESYMBOL.	Designer Service
SYMBOLCANDELETEROOT	Delete root symbols. Must be used with SYMBOL, SYMBOLDELETE.	Designer Service
SYMBOLCREATE	Create symbols. Must be used with SYMBOL.	Designer Service
SYMBOLDELETE	Delete symbols. Must be used with SYMBOL.	Designer Service
SYMBOLREMOVE	Remove symbols from a hierarchy. Must be used with SYMBOL.	Designer Service
SYMBOLSET	Modify symbols. Must be used with SYMBOL.	Designer Service
SYMBOLSWITCH	Switch symbols in a hierarchy. Must be used with SYMBOL.	Designer Service
SYSTEMATTRIBUTECREATE	Create system attributes. Must be used with ATTRIBUTE.	Designer Service
SYSTEMATTRIBUTEDELETE	Delete system attributes. Must be used with ATTRIBUTE.	Designer Service
SYSTEMATTRIBUTEMODIFY	Modify system attributes. Must be used with ATTRIBUTE.	Designer Service
USERADMINISTRATION	Perform user administration	Does not apply
USERATTRIBUTECREATE	Create user attributes. Must be used with ATTRIBUTE.	Designer Service
USERATTRIBUTEDELETE	Delete user attributes. Must be used with ATTRIBUTE.	Designer Service
USERATTRIBUTEMODIFY	Modify user attributes. Must be used with ATTRIBUTE.	Designer Service
USERRESETPASSWORD	Reset passwords.	Does not apply
USERSYMBOLACCESS	Manage symbol access for users.	Does not apply
VIEWDATA	View data.	Designer Power User Viewer Service
WORKFLOWDESIGNER	Access Longview Workflow Designer.	Designer

• ObjectType is GROUP and is used only when OperationName is USERADMINISTRATION or USERRESETPASSWORD.
• ObjectName is the group which the authorization specified for OperationName is applied to. ObjectName is used only when OperationName is USERADMINISTRATION or USERRESETPASSWORD.

Note: If ObjectName is AllUsers, the specified authorization is granted to the user for all users in the system.
For more information, see Understanding the AllUsers Group.

Syntax examples:

Preparing import files for user symbol access

To set the symbol access for several users at the same time, you must create an item file that lists the symbol access for users, each parameter on a separate line. In this fashion, you can set as many parameters for as many users as you like.

Item file syntax

Create a new text file, and for each symbol authorization granted to a particular user, include the following:

USER{UserName{SymAccessRole{DimName{Inherit{SymName{Access{NumLevels{Priority

where:

• UserName is the name of the user to whom the access is being granted.
• SymAccessRole is the name of the symbol access role in which the symbol access being granted resides.
• DimName is the dimension to which Access refers.
• Inherit indicates whether the access is inherited from the symbol access role itself and is either TRUE or FALSE.
• SymName is the name of a symbol to which access is being granted. This needs to be set only if inherit is set to FALSE.
• Access is either R (read) or W (write). This needs to be set only if inherit is set to FALSE.
• NumLevels is how many levels below this symbol in the hierarchy access is granted. This needs to be set only if inherit is set to FALSE.
• Priority is a number greater than zero designating the precedence for the access type, where 1 is the highest priority and a priority of 0 gives precedence to any other non-zero value. This needs to be set only if inherit is set to FALSE.

Syntax examples:

Importing files

To import the files that you have created, follow these steps:

1. Open Longview Application Administrator.
2. Select File > Import. The Import dialog opens, shown below:

   

3. For Item type, select the appropriate server object in the list, and click Next.
4. In the Item file field, click Next.
5. Do one of the following:
   • If you are importing symbols, select the dimension in which to create the new symbols, and click Next.
   • Otherwise, continue to the next step.
6. On the file locations page, type the Item file Location.
7. Depending on the type of file you are importing, complete the following fields, as necessary:

   1. Description file (optional): Optionally, select Include descriptions. For Description file Location, type the location of the description filed. This applies to Attributes, Schedules, Symbols, and Symbol access roles.

   2. Group membership file (optional): Optionally, select Include group memberships. For Group membership file Location, type the location of the group membership file. This applies to Users and Groups.

   3. Parent-child file (optional): Optionally, select Include parent-child relationships. For Parent-child file Location, type the location of the parent-child file. This applies to Symbols.

   Note: You can also click Browse to navigate to, and select, the desired file.

8. Click Finish. An Import Summary dialog opens, informing you of any errors.