This section describes the settings within the Web.config file that you can configure to customize the Microsoft Dynamics SL Web Apps for your business. These settings apply to all users and devices for the deployment.
The Web.config file exists in the folder that you specified in Physical File Location on the Site Information tab in Microsoft Dynamics SL Web Configuration Console. For more information, see
“Deploy Microsoft Dynamics SL Web Apps” on page 15.
These settings are located in the <appSettings> section of the Web.config file.
AttachmentMaxSizeMegabytes
Description: The maximum file size of an uploaded attachment, expressed in megabytes (MB). If a file exceeding this limit is uploaded, the upload will fail, and an error will be logged.
Valid Values: Non-negative integers less than 2147 Default Value: 5
Example 1: Attachments that have a file size up to ten megabytes may be uploaded <add key="AttachmentMaxSizeMegabytes" value="10" />
Example 2: Attachments may not be uploaded
<add key="AttachmentMaxSizeMegabytes" value="0" />
Companies
Description: The list of companies that appear in at login.
Valid Values: all; db:<appDBname>; <id1>,<id2>
Default Value: all
Example 1: All companies associated with a single Microsoft Dynamics SL system database <add key="Companies" value="all" />
Example 2: All companies associated with a single Microsoft Dynamics SL application database <add key="Companies" value="db:SLDemoApp60" />
Example 3: Specific company ID(s) 0010 and 0060
<add key="Companies" value="0010,0060" />
LoginPersistence
Description: How long the cookie saved on the client device remains before it expires. This cookie stores the settings on the Settings pages.
Valid Values: month:1 - month:12; 1 - 31 (days) Default Value: month:1
Example 1: Nine months
<add key="LoginPersistence" value="month:9" />
Example 2: Twenty days
<add key="LoginPersistence" value="20" />>
MaximumDays
Description: Maximum number of days to display in a Timecard period.
Valid Values: month; 1-31 (days) Default Value: month
Example 1: A month
<add key="MaximumDays" value="month" />
Example 2: Twenty-one days
<add key="MaximumDays" value="21" />
MenuTiles
Description: Toggles between the classic menu interface and the new Tile based menu interface.
Valid Values: True, False Default Value: False
<add key="MenuTiles" value="False" />
The files for the menu tiles are stored under the SLWebApps folder in the Tiles folder. If you would like to use your own tiles they can be re-named to the file name of the tiles you want to replace and then copy them to this folder. The only stipulation is that the files be in .png file format and be sized to 100px by 100px. Conversely, you can change the tile location and file names in the System database .SQL file where the menu entries are created. In the SQL snippet below the file location and file names are set with the parameter ‘src=’…
delete from WebAppMenu where Origin = '[DynamicsSL]' exec AddWebAppsMenuEntry
100,'GroupMenuCollapse','Project','MENU','PA,TM=TM','','src="/Tiles/project.png"',0,'RejectedTimecardExists,Reje ctedExpenseExists,ApprovalsExists,LineApprovalsExists'
exec AddWebAppsMenuEntry 101,'ScreenEntry','Timecard
Entry','MDTMTCE','ProjectTimecard','Periods','src="/Tiles/TimeCardEntry.png"',0,'RejectedTimecardExists' exec AddWebAppsMenuEntry 102,'ScreenEntry','Expense
Entry','MDTMTEE','ProjectExpense','ExpenseGrid','NewDoc=Yes;src="/Tiles/ExpenseEntry.png"',1,'RejectedExpenseExi sts'
etc.…
PhoneFormat
Description: Override default date format Valid Values: Regular expressions (regex) Default Value: No entry
The default phone format in web apps is US format (nnn) nnn-nnnn nnnn. To override this the user can use regular expressions for their own format. A web.config entry with the key “PhoneFormat” would be added.
Example 1: The default US format (nnn) nnn-nnnn nnnn would be defined as this regular expression <add key="PhoneFormat" value='^(\d\d\d)(\d{3})(\d{0,4})(\d{4,4})*@($1) $2-$3
$4'/>
Example 2: The format nnn.nnn.nnnn nnnn would be defined as this regular expression
<add key="PhoneFormat" value='^(\d\d\d)(\d{3})(\d{0,4})(\d{4,4})*@$1.$2.$3
$4'/>
ReportQueueAutoRefresh
Description: Initial state of auto refresh.
Valid Values: True, False Default Value: True
Example: When each user opens the Report Queue, auto refresh is turned off. The user has the choice to tap Auto Refresh to toggle it on.
<add key="ReportQueueAutoRefresh" value="true" />
ReportQueueRefreshDelay
Description: Number of seconds between auto refresh.
Valid Values: Any positive integer number Default Value: 60
Example: Auto Refresh every two minutes.
<add key="ReportQueueRefreshDelay" value="120" />
ReportQueueRefreshCount
Description: Number of times to sequentially auto refresh.
Valid Values: Any positive integer number Default Value: 10
Example: The Report Queue will automatically refresh 5 times in a row.
<add key="ReportQueueRefreshCount" value="5" />
SessionPasswordRetries
Description: Password retries before warning.
Valid Values: 1 to 10 Default Value: 5
Example: Four retries
<add key="SessionPasswordRetries" value="4" />
Theme
Description: Default theme for all devices. This setting is superseded if the user specifies a theme in Settings. The user can revert to the Web.config setting by tapping or clicking Reset Settings in Settings.
Valid Values: Base, Dynamics, Black, Gray, Custom Default Value: Base
Example: Black theme
<add key="Theme" value="Black" />
ThemePersistence
Description: How long the cookie saved on the client device remains before it expires. This cookie stores the theme choice on the Theme page.
Valid Values: month:1 - month:12 Default Value: month:12
Example: Three months
<add key="ThemePersistence" value="month:3" />
TimecardPeriodCount
Description: Controls the number of period ending dates to display on the Open Timecards page.
This includes future periods as controlled by the TimecardPeriodFuture Web.config setting. This setting is superseded if the user sets a default in Settings in Timecard Entry. The user can revert to the Web.config setting by tapping or clicking Reset Settings in Settings.
Valid Values: 5, 10, 15, 20 Default Value: 20
Example: Fifteen periods
<add key="TimecardPeriodCount" value="15" />
TimecardPeriodFuture
Description: Controls the number of future timecard periods to display on the Current Entry page.
A future timecard period is any period that contains a week ending date after the current business date.
Valid Values: Numeric value from 1 to one less than the TimecardPeriodCount value.
Default Value: 1
Example: Twelve periods
<add key="TimecardPeriodFuture" value="12" />
TimecardPFTOvertimeReduce
Description: Control the behavior of regular hours editing. If True then Overtime hours will reduce the amount of regular hours when entered. If False the Regular hours calculation is decoupled from the Overtime hours.
Valid Values: True/False
Default Value: True (this can be modified) Example: Fifteen periods
<add key="TimecardPFTOvertimeReduce" value="True" />
WindowsLogin
Description: Login type of Windows user or Microsoft Dynamics SL user.
Valid Values: True, False Default Value: True
Example: Microsoft Dynamics SL user
<add key="WindowsLogin" value="False" />
Note: If you set WindowsLogin to False, you must set up a password in Microsoft Dynamics SL for each user who logs in to Web Apps. Each user can set their own password by logging on to Microsoft Dynamics SL, and then clicking Set Password on the Tools menu. They should leave the Old Password blank if this is their first Microsoft Dynamics SL password. Or, an administrator can set the initial password of behalf of each user in User Maintenance (95.260.00).