The following properties are available within the web.config files of each Portal. Where noted some options are specific to certain Portals.

Each Portal website contains a web.config file used to define core settings not found in the B1 add-on. Ensure that all web.config files are backed up prior to applying edits.

Properties: configuration - appSettings

The following properties are found in the Portal’s web.config file, under <configuration> <appSettings>. For example:

<configuration>
  <!-- ... other settings ... -->

  <appSettings>
    <add key="someProperty" value="someValue" />
    <!-- ... other properties ... -->
  </appSettings>

  <!-- ... other settings ... -->
</configuration>
Property Portal Description
AllowSalesPersonOverride Employee Portal Valid values: true or false (Default is false).

Example 1 - Enable Sales Person Override:

<add key="AllowSalesPersonOverride" value="true" />

Example 2 - Disable Sales Person Override:

<add key="AllowSalesPersonOverride" value="false" />

By default (when disabled), the customer’s default sales employee is assigned to all orders.

When enabled, the sales employee placing the order is the one assigned to the order. Note that this may happen when users who have the Sales Manager or Sales Exec role place an order on behalf of other employee’s customers.
AlternateHome Employee Portal Default value: Dashboard/Index

Example - Setting AlternateHome back to default:

<add key="AlternateHome" value="Dashboard/Index" />

This property sets the default login location for users logging into Employee Portal.
EnableEmployeeLogin Customer Portal Valid values: true or false

Example 1 - Enable Employee Login:

<add key="EnableEmployeeLogin" value="true" />

Example 2 - Disable Employee Login:

<add key="EnableEmployeeLogin" value="false" />

When enabled, licensed Employee users may access Customer Portal Sales User functionality.
oBeerTheme Customer Portal Valid values: true or false

Requires oBeer. When disabled, this will use the standard Portal theme.
OBeerTheme Employee Portal Valid values: true or false

Requires oBeer. When disabled, this will use the standard Portal theme.
OPRoleBackwardCompabilityEnabled Customer Portal Valid values: true or false

Example 1 - Enable Backward Compatibility for Order Pad:

<add key="OPRoleBackwardCompabilityEnabled" value="true" />

Example 2 - Disable Backward Compatibility for Order Pad:

<add key="OPRoleBackwardCompabilityEnabled" value="false" />

As of version 93.6, when enabled, this allows “Order” role to access both Orders and Quotes functionality, as per application licensing and configuration settings. This setting does not impact Quote role.
SalesUserAttachmentAcceptTypes Employee Portal Default value: doc,docx,pdf,xls,xlsx,ppt,pptx,mpp,zip,jpg,jpeg,png,gif,tif,tiff,txt

Example 1 - Setting Sales User attachment types back to default:

<add key="SalesUserAttachmentAcceptTypes" value="doc,docx,pdf,xls,xlsx,ppt,pptx,mpp,zip,jpg,jpeg,png,gif,tif,tiff,txt" />

Example 2 - Restrict Sales User attachment types to basic images only:

<add key="SalesUserAttachmentAcceptTypes" value="jpg,jpeg,png,gif,tif,tiff" />

This property defines the list of file extensions that will be accepted when uploading attachments within Sales User features.
SearchServiceUrl Customer Portal This defines the B2B Search index api URL, which is used by a B2B-enabled Customer Portal to load web items. Requires /api at the end.

Example: if the B1Search Index is installed on localhost:5000, then the Search Service would be as follows:

<add key="SearchServiceUrl" value="http://localhost:5000/api" />

Properties: configuration - system.web - httpRuntime

The property httpRuntime found under system.web includes the option for maxRequestLength. maxRequestLength places a limit on the size of files uploaded to the Portal. By default, this is set to maxRequestLength="10240" (10MB). Note that B1WebAPI has its own file size limitations, so when uploading files to B1, such as Activity or Document attachments, maxRequestLength will be further restricted to no more than 4MB.

In context this can be defined as follows:

<configuration>
  <!-- ... other settings ... -->

  <system.web>
    <httpRuntime maxRequestLength="10240" executionTimeout="1200" />
    <!-- ... other settings ... -->
  </system.web>  

  <!-- ... other settings ... -->
</configuration>