Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

CURR (Col A)

Mandatory in template or in PARAM = mandatory in template or in PARAM (FORMS)

 Optional in column A= optional in Column A (REPORTS)                                                                                                                                        

Parameter

Mandatory/Optional

Value (example)

Comment

FORMS

REPORT

CURR

Mandatory in template or in PARAM

Optional in column A

SEK

Define currency for each CVAL column. Can be defined in column A, row 1, OR in PARAM.

CURR is a FORM specific parameter, which is mandatory either in column A, row 1, or in PARAM. When updating values in the database, the data rows need to be tagged to a specific currency in order to keep the updated data cells separated and not risk that existing data would be updated with incorrect data. Even though the values registered in the form might not be money, a currency code must always be defined.

This parameter can also be used in REPORTS if data from the Bizview data view (in which FORM data is updated) is used in the report. Then, one specific currency may need to be specified in order to get the correct numbers in the report; however, that is only the case if data is registered in several different currencies.

Note: CURR can only be defined in ONE place, either in column A (for each CVAL column), in row 1 (for each DATA row), or in PARAM.

If a template only contains one currency, then it is best to state CURR once in the PARAM sheet. However, CURR can also be stated in column A and defined for each CVAL column. If a template contains several currencies for different CVAL columns, then CURR must be defined in column A.

If spread groups are used in the template, then only one currency can be defined within one SPGROUP. However, different currencies can be stated in different spread groups.

The CURR row should be defined with ROWTYPE = DESIGN (the row will be hidden when the document is generated).

CURR(ColA)

Published:

CURR (Col A)

Mandatory in template or in PARAM = mandatory in template or in PARAM (FORMS)

 Optional in column A= optional in Column A (REPORTS)                                                                                                                                        

Parameter

Mandatory/Optional

Value (example)

Comment

FORMS

REPORT

CURR

Mandatory in template or in PARAM

Optional in column A

SEK

Define currency for each CVAL column. Can be defined in column A, row 1, OR in PARAM.

CURR is a FORM specific parameter, which is mandatory either in column A, row 1, or in PARAM. When updating values in the database, the data rows need to be tagged to a specific currency in order to keep the updated data cells separated and not risk that existing data would be updated with incorrect data. Even though the values registered in the form might not be money, a currency code must always be defined.

This parameter can also be used in REPORTS if data from the Bizview data view (in which FORM data is updated) is used in the report. Then, one specific currency may need to be specified in order to get the correct numbers in the report; however, that is only the case if data is registered in several different currencies.

Note: CURR can only be defined in ONE place, either in column A (for each CVAL column), in row 1 (for each DATA row), or in PARAM.

If a template only contains one currency, then it is best to state CURR once in the PARAM sheet. However, CURR can also be stated in column A and defined for each CVAL column. If a template contains several currencies for different CVAL columns, then CURR must be defined in column A.

If spread groups are used in the template, then only one currency can be defined within one SPGROUP. However, different currencies can be stated in different spread groups.

The CURR row should be defined with ROWTYPE = DESIGN (the row will be hidden when the document is generated).

CURR(ColA)

For an optimal Community experience, Please view on Desktop
Powered by Zendesk