FIELDBOSS Policy on Client-Specific Customizations
FIELDBOSS is designed as an out-of-the-box solution built as a layer on top of Dynamics 365 Sales and Dynamics 365 Business Central. It is intended to be configured for each FIELDBOSS client, but not customized by clients.
Microsoft provides tools for modifying the Dynamics platform, however, making unauthorized changes to a FIELDBOSS environment can impact the FIELDBOSS functionality, causing system errors, broken processes, and / or data integrity issues, and can also limit Rimrock’s ability to support or upgrade the environment.
There are other solutions available for Dynamics that add on functionality, both from Microsoft and from ISV companies. However, adding an app or add-on solution to a FIELDBOSS environment alters the system like a customization and comes with the same risks as unauthorized customizations. Rimrock does not support the installation of apps or add-ons to a FIELDBOSS environment including Business Central add-ons.
FIELDBOSS provides its own model driven apps for accessing FIELDBOSS environments. Microsoft also provides other model driven apps (such as “Sales Hub”) but these apps do not contain the FIELDBOSS coding that is essential for data integrity in a FIELDBOSS environment. The use of these other model driven apps with FIELDBOSS is not supported.
Rimrock will support (on an hourly basis) some client-specific customizations as per the guidelines in this document. Customizations should be considered only when there is a critical requirement directly related to FIELDBOSS. It is strongly recommended that customizations are reviewed by Rimrock prior to proceeding or performed by Rimrock.
Client-specific customizations will impact the cost and timing of upgrades and can cause additional billable support that we cannot estimate in advance. They are not included in the normal FIELDBOSS support or licensing.
Clients are responsible for tracking all customizations made using the Dynamics 365 customization tool set. This includes all customizations, whether requested to be built by Rimrock or built by the client themselves.
This document describes different types of customizations and the level to which they are supported. Anything not described in this document is not supported.
BEST PRACTICE: all client specific customizations should be done within a client specific unmanaged solution that uses a client specific publisher. Customization should be built in a sandbox environment and tested before they are installed in a production environment.
FIELDBOSS Customization Details
Fields
| Type |
Not Supported |
Limited Support |
Fully Supported |
Additional Clarification |
| Simple Field (create new) |
|
|
X |
|
| Auto-Number (create new) |
X |
|
|
|
| Option Set (create new) |
|
|
X |
|
| Global Option Set (create new) |
|
|
X |
|
| Multi-Select Field (create new) |
|
X |
|
Should be tested to make sure the desired result is achieved; mobile supports these
fields, but document templates may not.
|
| Calculated (create new) |
|
|
X |
|
| Rollup Field (create new) |
|
X |
|
Design approval required. Microsoft limits the number of rollup fields.
|
| Lookup Field (create new) |
|
X |
|
Design approval required. Adding a lookup field creates relationship between entities
and can have an unpredictable impact on the system (i.e. performance, cascading
behavior).
|
| Field Controls |
|
X |
|
Approval required. Some controls may not be supported and should be tested to make sure
the desired result is achieved.
|
| Custom Field Requirement |
|
X |
|
Design approval required. Making a custom field required could impact FIELDBOSS
processes.
|
| FIELDBOSS Fields (modify) |
X |
|
|
For example, the following are NOT SUPPORTED: – expanding the size of a FIELDBOSS text
field – modifying a FIELDBOSS option set – changing a FIELDBOSS field from “required” to
“optional” – renaming a FIELDBOSS field (form labels can be edited)
|
| Type |
Simple Field (create new) |
| Supported |
Fully Supported |
| Type |
Auto-Number (create new) |
| Supported |
Not Supported |
| Type |
Option Set (create new) |
| Supported |
Fully Supported |
| Type |
Global Option Set (create new) |
| Supported |
Fully Supported |
| Type |
Multi-Select Field (create new) |
| Supported |
Limited Support |
| Additional Clarification |
Should be tested to make sure the desired result is achieved; mobile supports these
fields, but document templates may not.
|
| Type |
Calculated (create new) |
| Supported |
Fully Supported |
| Type |
Rollup Field (create new) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required. Microsoft limits the number of rollup fields.
|
| Type |
Lookup Field (create new) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required. Adding a lookup field creates relationship between entities
and can have an unpredictable impact on the system (i.e. performance, cascading
behavior).
|
| Type |
Field Controls |
| Supported |
Limited Support |
| Additional Clarification |
Approval required. Some controls may not be supported and should be tested to make sure
the desired result is achieved.
|
| Type |
Custom Field Requirement |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required. Making a custom field required could impact FIELDBOSS
processes.
|
| Type |
FIELDBOSS Fields (modify) |
| Supported |
Not Supported |
| Additional Clarification |
For example, the following are NOT SUPPORTED:
– expanding the size of a FIELDBOSS
text field
– modifying a FIELDBOSS option set
– changing a FIELDBOSS field
from “required” to “optional”
– renaming a FIELDBOSS field (form labels can be
edited)
|
Please Note: Adding fields can affect storage requirements and performance.
Best Practice: Keep the number of fields limited to what is absolutely necessary.
Forms
| Type |
Not Supported |
Limited Support |
Fully Supported |
Additional Clarification |
| Custom Fields (add) |
|
|
X |
It’s important to note that adding too many fields to a form can impact load time and
general usability.
|
| Custom Quick View (add) |
|
X |
|
Design approval required. Must be configured by Rimrock. |
| Custom Read Only Subgrid (add) |
|
|
X |
|
| Custom Editable Subgrid (add) |
|
X |
|
Design approval required. Must be configured by Rimrock; configuring them incorrectly can
lead to data integrity issues.
|
| Custom Section (add) |
|
|
X |
|
| Custom Tab (add) |
|
|
X |
|
| Custom Main Form (add) |
|
X |
|
Design approval required. Must be configured by Rimrock; can add cost to upgrades.
|
| Custom Quick Create (add) |
|
X |
|
Design approval required. Must be configured by Rimrock; can add cost to upgrades.
|
| FIELDBOSS field (move) |
|
X |
|
Can move within a section or hide it and re-add it to a new section.
|
| FIELDBOSS field (relabel on form) |
|
X |
|
Not recommended. Makes the environment more difficult to support.
|
| FIELDBOSS field (remove) |
X |
|
|
Hide it on the form instead. |
| FIELDBOSS Quick View (move) |
X |
|
|
Can move within a section or hide it and re-add it to a new section.
|
| FIELDBOSS Quick View (rename) |
X |
|
|
Can hide it and create new custom one. |
| FIELDBOSS Quick View (remove) |
X |
|
|
Hide it on the form instead. |
| FIELDBOSS Subgrid (move) |
X |
|
|
Moving Subgrids will cause form merge issues on upgrades |
| FIELDBOSS Subgrid (rename) |
X |
|
|
Renaming subgrids can break FIELDBOSS code used on the form. |
| FIELDBOSS Subgrid (remove) |
X |
|
|
Hide the subgrid on the form instead. |
| FIELDBOSS Section (move) |
X |
|
|
Moving Sections will cause form merge issues on upgrades |
| FIELDBOSS Section (rename) |
X |
|
|
Renaming sections can break FIELDBOSS code used on the form. |
| FIELDBOSS Section (remove) |
X |
|
|
Hide it on the form instead. |
| FIELDBOSS Tab (move) |
|
X |
|
Design approval required. Must be configured by Rimrock. |
| FIELDBOSS Tab (rename) |
X |
|
|
Renaming tabs can break FIELDBOSS code used on the form. |
| FIELDBOSS Tab (remove) |
X |
|
|
Hide it on the form instead. |
| FIELDBOSS Form (rename) |
X |
|
|
Hide it on the form instead. |
| FIELDBOSS Form (deactivate) |
X |
|
|
|
| FIELDBOSS Form (delete) |
X |
|
|
|
| FIELDBOSS Form (properties) |
X |
|
|
|
| FIELDBOSS Form (form security) |
X |
|
|
|
| FIELDBOSS Form Events (modify) |
X |
|
|
(For example, JavaScript) |
| Form Controls (add / modify) |
|
X |
|
Only supported on custom forms. |
| Type |
Custom Fields (add) |
| Supported |
Fully Supported |
| Additional Clarification |
It’s important to note that adding too many fields to a form can impact load time and
general usability.
|
| Type |
Custom Quick View (add) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required. Must be configured by Rimrock. |
| Type |
Custom Read Only Subgrid (add) |
| Supported |
Fully Supported |
| Type |
Custom Editable Subgrid Set (add) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required. Must be configured by Rimrock; configuring them incorrectly can
lead to data integrity issues.
|
| Type |
Custom Section (add) |
| Supported |
Fully Supported |
| Type |
Custom Tab (add) |
| Supported |
Fully Supported |
| Type |
Custom Main Form (add) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required. Must be configured by Rimrock; can add cost to upgrades.
|
| Type |
Custom Quick Create (add) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required. Must be configured by Rimrock; can add cost to upgrades.
|
| Type |
FIELDBOSS field (move) |
| Supported |
Limited Support |
| Additional Clarification |
Can move within a section or hide it and re-add it to a new section.
|
| Type |
FIELDBOSS field (relabel on form) |
| Supported |
Limited Support |
| Additional Clarification |
Not recommended. Makes the environment more difficult to support.
|
| Type |
FIELDBOSS field (remove) |
| Supported |
Not Supported |
| Additional Clarification |
Hide it on the form instead. |
| Type |
FIELDBOSS Quick View (move) |
| Supported |
Not Supported |
| Additional Clarification |
Can move within a section or hide it and re-add it to a new section.
|
| Type |
FIELDBOSS Quick View (rename) |
| Supported |
Not Supported |
| Additional Clarification |
Can hide it and create new custom one. |
| Type |
FIELDBOSS Quick View (remove) |
| Supported |
Not Supported |
| Additional Clarification |
Hide it on the form instead. |
| Type |
FIELDBOSS Subgrid (move) |
| Supported |
Not Supported |
| Type |
FIELDBOSS Subgrid (rename) |
| Supported |
Not Supported |
| Additional Clarification |
Renaming subgrids can break FIELDBOSS code used on the form.
|
| Type |
FIELDBOSS Subgrid (remove) |
| Supported |
Not Supported |
| Additional Clarification |
Hide it on the form instead. |
| Type |
FIELDBOSS Section (move) |
| Supported |
Not Supported |
| Type |
FIELDBOSS Section (rename) |
| Supported |
Not Supported |
| Additional Clarification |
Renaming sections can break FIELDBOSS code used on the form.
|
| Type |
FIELDBOSS Section (remove) |
| Supported |
Not Supported |
| Additional Clarification |
Hide it on the form instead. |
| Type |
FIELDBOSS Tab (move) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required. Must be configured by Rimrock. |
| Type |
FIELDBOSS Tab (rename) |
| Supported |
Not Supported |
| Additional Clarification |
Renaming tabs can break FIELDBOSS code used on the form. |
| Type |
FIELDBOSS Tab (remove) |
| Supported |
Not Supported |
| Additional Clarification |
Hide it on the form instead. |
| Type |
FIELDBOSS Form (rename) |
| Supported |
Not Supported |
| Additional Clarification |
Hide it on the form instead. |
| Type |
FIELDBOSS Form (deactivate) |
| Supported |
Not Supported |
| Additional Clarification |
Hide the subgrid on the form instead. |
| Type |
FIELDBOSS Form (delete) |
| Supported |
Not Supported |
| Additional Clarification |
Hide the subgrid on the form instead. |
| Type |
FIELDBOSS Form (properties) |
| Supported |
Not Supported |
| Additional Clarification |
Hide the tab on the form instead. |
| Type |
FIELDBOSS Form (form security) |
| Supported |
Not Supported |
| Type |
FIELDBOSS Form Events (modify) |
| Supported |
Not Supported |
| Additional Clarification |
(For example, JavaScript) |
| Type |
Form Controls (add / modify) |
| Supported |
Not Supported |
| Additional Clarification |
Only supported on custom forms. |
Please Note: When FIELDBOSS is upgraded, the FIELDBOSS versions of the forms are imported back into the system and Dynamics 365 will attempt to merge it with the custom form.
Best Practice: Whenever possible, make form changes within your own custom sections to simplify the merge process on upgrades.
Views, Charts, & Dashboards
| Type |
Not Supported |
Limited Support |
Fully Supported |
Additional Clarification |
| Add Custom View |
|
|
X |
|
| FIELDBOSS Views (deactivate) |
|
|
X |
|
| FIELDBOSS Views (modify) |
|
X |
|
Use “Save As” to create a custom view for a better upgrade experience.
|
| FIELDBOSS Views (delete) |
X |
|
|
|
| Add Custom Chart |
|
|
X |
|
| FIELDBOSS Chart (deactivate) |
|
|
X |
|
| FIELDBOSS Chart (modify) |
|
X |
|
Use “Save As” to create a custom chart for a better upgrade experience.
|
| FIELDBOSS Chart (delete) |
X |
|
|
|
| Add Custom Dashboard |
|
|
X |
|
| FIELDBOSS Dashboard (deactivate) |
|
|
X |
|
| FIELDBOSS Dashboard (modify) |
|
X |
|
Use “Save As” to create a custom dashboard for a better upgrade experience.
|
| FIELDBOSS Dashboard (delete) |
X |
|
|
|
| Type |
Add Custom view |
| Supported |
Fully Supported |
| Type |
FIELDBOSS Views (deactivate) |
| Supported |
Fully Supported |
| Type |
FIELDBOSS Views (modify) |
| Supported |
Limited Support |
| Additional Clarification |
Use “Save As” to create a custom view for a better upgrade experience.
|
| Type |
FIELDBOSS Views (delete) |
| Supported |
Not Supported |
| Type |
Add Custom Chart |
| Supported |
Fully Supported |
| Type |
FIELDBOSS Chart (deactivate) |
| Supported |
Fully Supported |
| Type |
FIELDBOSS Chart (modify) |
| Supported |
Limited Support |
| Additional Clarification |
Use “Save As” to create a custom chart for a better upgrade experience.
|
| Type |
FIELDBOSS Chart (delete) |
| Supported |
Not Supported |
| Type |
Add Custom Dashboard |
| Supported |
Fully Supported |
| Type |
FIELDBOSS Dashboard (deactivate) |
| Supported |
Fully Supported |
| Type |
FIELDBOSS Dashboard (modify) |
| Supported |
Limited Support |
| Additional Clarification |
Use “Save As” to create a custom dashboard for a better upgrade experience.
|
| Type |
FIELDBOSS Dashboard (delete) |
| Supported |
Not Supported |
Please Note: When FIELDBOSS is upgraded, the FIELDBOSS versions of the views, charts, and dashboards are imported back into the system.
Best Practice: Whenever possible, rather than modifying a FIELDBOSS view, chart or dashboard, use the “save as” to create a new custom copy and move the newly created one instead.
Entities & Relationships
| Type |
Not Supported |
Limited Support |
Fully Supported |
Additional Clarification |
| Custom Entity (create) |
|
X |
|
Design approval required – must be configured by Rimrock.
|
| Custom Relationship (create) |
|
X |
|
Design approval required – must be configured by Rimrock.
|
|
FIELDBOSS Relationship – Behaviour (modify)
|
X |
|
|
|
|
FIELDBOSS Relationship – Field Mappings (remove)
|
X |
|
|
|
|
FIELDBOSS Relationship – Field Mappings (add)
|
|
X |
|
Design approval required – must be configured by Rimrock.
|
| Entity Metadata (modify) |
|
X |
|
Design approval required – must be configured by Rimrock (i.e. allow quick create, enable notes, etc.).
|
| Type |
Custom Entity (create) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required – must be configured by Rimrock.
|
| Type |
Custom Relationship (create) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required – must be configured by Rimrock.
|
| Type |
FIELDBOSS Relationship – Behaviour (modify)
|
| Supported |
Not Supported |
| Type |
FIELDBOSS Relationship – Field Mappings (remove)
|
| Supported |
Not Supported |
| Type |
FIELDBOSS Relationship – Field Mappings (add)
|
| Supported |
Limited Support |
| Additional Clarification |
Design approval required – must be configured by Rimrock.
|
| Type |
Entity Metadata (modify) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required – must be configured by Rimrock (i.e. allow quick create, enable notes, etc.).
|
Please Note: Microsoft limits the number of custom entities that can be accessed by certain license types.
Security Roles, Form & Field Security
| Type |
Not Supported |
Limited Support |
Fully Supported |
Additional Clarification |
| Custom Security Role (create) |
|
|
X |
|
| FIELDBOSS Role (modify) |
X |
|
|
|
| Field Security (add) |
|
X |
|
Only supported on custom fields. |
| Form Security (modify) |
|
X |
|
Only supported on custom fields. |
| Type |
Custom Security Role (create) |
| Supported |
Fully Supported |
| Type |
FIELDBOSS Role (modify) |
| Supported |
Not Supported |
| Type |
Field Security (add) |
| Supported |
Limited Support |
| Additional Clarification |
Only supported on custom fields. |
| Type |
Form Security (modify) |
| Supported |
Limited Support |
| Additional Clarification |
Only supported on custom fields. |
Please Note: When FIELDBOSS is upgraded, the FIELDBOSS versions of security
roles are imported back into the system.
Best Practice: Always assign one or more FIELDBOSS security roles to all users,
and only use a custom role to assign an additional privilege.
Processes
| Type |
Not Supported |
Limited Support |
Fully Supported |
Additional Clarification |
| Custom Business Rule (add) |
|
X |
|
Design approval required – must be configured by Rimrock to ensure it does not conflict with FIELDBOSS.
|
| FIELDBOSS Business Rule (modify) |
X |
|
|
|
| Cloud Flow (add) |
|
X |
|
Design approval required – must be configured by Rimrock to ensure it does not conflict with FIELDBOSS.
|
| Data Flow (add) |
X |
|
|
|
| Desktop Flow (add) |
X |
|
|
|
| FIELDBOSS Flow (modify) |
X |
|
|
|
| Workflow (add) |
|
X |
|
Design approval required – must be configured by Rimrock to ensure it does not conflict with FIELDBOSS.
|
| FIELDBOSS Workflows (modify) |
|
X |
|
Design approval required – must be configured by Rimrock to ensure it does not conflict with FIELDBOSS.
|
| Dialogs (add) |
X |
|
|
Microsoft has announced that dialogs will be deprecated soon.
|
| Business Process Flows (add) |
X |
|
|
|
| Actions (add) |
|
X |
|
Design approval required – must be created by Rimrock. |
| Type |
Custom Business Rule (add) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required – must be configured by Rimrock to ensure it does not conflict with FIELDBOSS.
|
| Type |
FIELDBOSS Business Rule (modify) |
| Supported |
Not Supported |
| Type |
Cloud Flow (add) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required – must be configured by Rimrock to ensure it does not conflict with FIELDBOSS.
|
| Type |
Data Flow (add) |
| Supported |
Not Supported |
| Type |
Desktop Flow (add) |
| Supported |
Not Supported |
| Type |
FIELDBOSS Flow (modify) |
| Supported |
Not Supported |
| Type |
Workflow (add) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required – must be configured by Rimrock to ensure it does not conflict with FIELDBOSS.
|
| Type |
FIELDBOSS Workflows (modify) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required – must be configured by Rimrock to ensure it does not conflict with FIELDBOSS.
|
| Type |
Dialogs (add) |
| Supported |
Not Supported |
| Additional Clarification |
Microsoft has announced that dialogs will be deprecated soon.
|
| Type |
Business Process Flows (add) |
| Supported |
Not Supported |
| Type |
Actions (add) |
| Supported |
Limited Support |
| Additional Clarification |
Design approval required – must be created by Rimrock. |
Advanced Customizations
| Type |
Not Supported |
Limited Support |
Fully Supported |
Additional Clarification |
| JavaScript (add custom) |
X |
|
|
|
| JavaScript (modify / disable) |
X |
|
|
|
| Plugins (add custom) |
X |
|
|
|
| Plugins (modify / disable) |
X |
|
|
|
| Site Map (modify) |
X |
|
|
|
| Canvas Apps (add custom) |
X |
|
|
|
| Canvas Apps (modify) |
X |
|
|
|
| Model Driven Apps (add custom) |
X |
|
|
|
| FIELDBOSS Model Driven Apps (modify) |
|
X |
|
Customizing the FIELDBOSS app is NOT supported unless approved by and configured by Rimrock.
|
| D365 App for Outlook (modify) |
|
X |
|
Can use and configure it as is supported by Microsoft, but as it is a desktop app, Rimrock’s ability to support is limited.
|
| D365 Addons (Microsoft) |
X |
|
|
Example: Field Service |
| D365 Addons (3rd Party) |
X |
|
|
Example: Click Dimensions |
| Integration Customizations |
X |
|
|
|
| Dynamics 365 Portals |
|
X |
|
Situation specific, speak with Rimrock for clarification |
| Copilot |
|
X |
|
Situation specific, speak with Rimrock for clarification |
| Type |
JavaScript (add custom) |
| Supported |
Not Supported |
| Type |
JavaScript (modify / disable) |
| Supported |
Not Supported |
| Type |
Plugins (add custom) |
| Supported |
Not Supported |
| Type |
Plugins (modify / disable) |
| Supported |
Not Supported |
| Type |
Site Map (modify) |
| Supported |
Not Supported |
| Type |
Canvas Apps (add custom) |
| Supported |
Not Supported |
| Type |
Canvas Apps (modify) |
| Supported |
Not Supported |
| Type |
Model Driven Apps (add custom) |
| Supported |
Not Supported |
| Type |
FIELDBOSS Model Driven Apps (modify) |
| Supported |
Limited Support |
| Additional Clarification |
Customizing the FIELDBOSS app is NOT supported unless approved by and configured by Rimrock.
|
| Type |
D365 App for Outlook (modify) |
| Supported |
Limited Support |
| Additional Clarification |
Can use and configure it as is supported by Microsoft, but as it is a desktop app, Rimrock’s ability to support is limited.
|
| Type |
D365 Addons (Microsoft) |
| Supported |
Not Supported |
| Additional Clarification |
Example: Field Service |
| Type |
D365 Addons (3rd Party) |
| Supported |
Not Supported |
| Additional Clarification |
Example: Click Dimensions |
| Type |
Integration Customizations |
| Supported |
Not Supported |
| Type |
Dynamics 365 Portals |
| Supported |
Limited Support |
| Additional Clarification |
Situation specific, speak with Rimrock for clarification |
| Type |
Copilot |
| Supported |
Limited Support |
| Additional Clarification |
Situation specific, speak with Rimrock for clarification |
Please Note: Advanced customizations can lead to support issues and extra cost on FIELDBOSS upgrades.
Best Practice: Work with a Rimrock consultant to find a way to meet your requirements without advanced customizations or to submit a product request to the Rimrock product team to have the product enhanced.
Reports & Templates
| Type |
Not Supported |
Limited Support |
Fully Supported |
Additional Clarification |
| Power BI Reports (modify) |
|
X |
|
FIELDBOSS out of the box reports should not be modified by clients. Rimrock can customize these reports for clients on request.
|
| Power BI Reports (create) |
|
X |
|
Clients can build their own reports, but Rimrock cannot support them.
|
| DCP Templates |
|
X |
|
Templates can be copied, then modified. |
| MS Excel Templates |
|
X |
|
Clients can create their own, but limited support is available.
|
| MS Word Templates |
|
X |
|
Clients can create their own, but limited support is available.
|
|
Dynamics 365 Reports (SSRS) (add custom)
|
|
X |
|
Clients can create their own, but limited support is available.
|
| Type |
Power BI Reports (modify) |
| Supported |
Limited Support |
| Additional Clarification |
FIELDBOSS out of the box reports should not be modified by clients. Rimrock can customize these reports for clients on request.
|
| Type |
Power BI Reports (create) |
| Supported |
Limited Support |
| Additional Clarification |
Clients can build their own reports, but Rimrock cannot support them.
|
| Type |
DCP Templates |
| Supported |
Limited Support |
| Additional Clarification |
Templates can be copied, then modified. |
| Type |
MS Excel Templates |
| Supported |
Limited Support |
| Additional Clarification |
Clients can create their own, but limited support is available.
|
| Type |
MS Word Templates |
| Supported |
Limited Support |
| Additional Clarification |
Clients can create their own, but limited support is available.
|
| Type |
Dynamics 365 Reports (SSRS) (add custom)
|
| Supported |
Limited Support |
| Additional Clarification |
Clients can create their own, but limited support is available.
|
Please Note: DCP templates are sometimes used in workflows (invoices for example) and alterations to the template can result in a breakdown of processes.
Best Practice – DCP: Always make a copy of a template before attempting to modify it.
Auditing
| Type |
Not Supported |
Limited Support |
Fully Supported |
Additional Clarification |
| Changing System Level |
X |
|
|
Should remain enabled. |
| Disabling Entity Level |
|
X |
|
Speak to a Rimrock Consultant. |
| Enabling Entity Level |
|
|
X |
|
| Disabling Field Level |
|
X |
|
Speak to a Rimrock Consultant. |
| Enabling Field Level |
|
|
X |
|
| Type |
Changing System Level |
| Supported |
Not Supported |
| Additional Clarification |
Should remain enabled. |
| Type |
Disabling Entity Level |
| Supported |
Limited Support |
| Additional Clarification |
Speak to a Rimrock Consultant. |
| Type |
Enabling Entity Level |
| Supported |
Fully Supported |
| Type |
Disabling Field Level |
| Supported |
Limited Support |
| Additional Clarification |
Speak to a Rimrock Consultant. |
| Type |
Enabling Field Level |
| Supported |
Fully Supported |
Please Note: Auditing logs are very important to our support team.
Best Practice: Enabling auditing on some entities can affect performance and storage requirements.
Mobile (Rimrock Consultants Only)
All mobile changes should be made by a Rimrock Consultant. Customizations to the standard mobile configuration add a custom layer that will need to be revisited on every upgrade, so they are discouraged unless truly necessary.
| Type |
Not Supported |
Limited Support |
Fully Supported |
Additional Clarification |
| Adding Additional Fields |
|
X |
|
Must be done by a Rimrock consultant. |
| Adding Custom Views |
|
X |
|
Must be done by a Rimrock consultant. |
| Adding Custom Charts |
|
X |
|
Must be done by a Rimrock consultant. |
| Adding Custom Forms |
|
X |
|
Must be scoped and approved by Mobile Manager. |
| Form Logic Changes |
|
X |
|
Must be scoped and approved by Mobile Manager. |
| Adding Tabs to Standard Forms |
|
X |
|
Must be scoped and approved by Mobile Manager. |
| Modifying FIELDBOSS Views |
|
X |
|
Must be scoped and approved by Mobile Manager. |
| Modifying FIELDBOSS Charts |
|
X |
|
Must be scoped and approved by Mobile Manager. |
| Modifying JavaScript |
|
X |
|
Must be done by Mobile Manager. |
| Modifying Sync Filters |
|
X |
|
Must be done by Mobile Manager. |
| Adding Custom Entities |
|
X |
|
Must be done by Mobile Manager; Potential Licensing impact.
|
| Altering Time Entry Logic |
|
X |
|
Must be scoped and approved by Mobile Manager. |
| Removing Tabs / Fields |
|
X |
|
Must be scoped and approved by Mobile Manager. |
|
Inspections Questionnaires Modifications
|
|
X |
|
Must be scoped and approved by Mobile Manager. |
| Inspections Views |
|
X |
|
Must be scoped and approved by Mobile Manager. |
| Resco Phone Settings |
|
X |
|
Must be done by a Rimrock consultant. |
| Resco Project Settings |
|
X |
|
Must be done by a Rimrock consultant. |
| Type |
Adding Additional Fields |
| Supported |
Limited Support |
| Additional Clarification |
Must be done by a Rimrock consultant. |
| Type |
Adding Custom Views |
| Supported |
Limited Support |
| Additional Clarification |
Must be done by a Rimrock consultant. |
| Type |
Adding Custom Charts |
| Supported |
Limited Support |
| Additional Clarification |
Must be done by a Rimrock consultant. |
| Type |
Adding Custom Forms |
| Supported |
Limited Support |
| Additional Clarification |
Must be scoped and approved by Mobile Manager. |
| Type |
Form Logic Changes |
| Supported |
Limited Support |
| Additional Clarification |
Must be scoped and approved by Mobile Manager. |
| Type |
Adding Tabs to Standard Forms |
| Supported |
Limited Support |
| Additional Clarification |
Must be scoped and approved by Mobile Manager. |
| Type |
Modifying FIELDBOSS Views |
| Supported |
Limited Support |
| Additional Clarification |
Must be scoped and approved by Mobile Manager. |
| Type |
Modifying FIELDBOSS Charts |
| Supported |
Limited Support |
| Additional Clarification |
Must be scoped and approved by Mobile Manager. |
| Type |
Modifying JavaScript |
| Supported |
Limited Support |
| Additional Clarification |
Must be done by Mobile Manager. |
| Type |
Modifying Sync Filters |
| Supported |
Limited Support |
| Additional Clarification |
Must be done by Mobile Manager. |
| Type |
Adding Custom Entities |
| Supported |
Limited Support |
| Additional Clarification |
Must be done by Mobile Manager; Potential Licensing impact.
|
| Type |
Altering Time Entry Logic |
| Supported |
Limited Support |
| Additional Clarification |
Must be scoped and approved by Mobile Manager. |
| Type |
Removing Tabs / Fields |
| Supported |
Limited Support |
| Additional Clarification |
Must be scoped and approved by Mobile Manager. |
| Type |
Inspections Questionnaires Modifications
|
| Supported |
Limited Support |
| Additional Clarification |
Must be scoped and approved by Mobile Manager. |
| Type |
Inspections Views |
| Supported |
Limited Support |
| Additional Clarification |
Must be scoped and approved by Mobile Manager. |
| Type |
Resco Phone Settings |
| Supported |
Limited Support |
| Additional Clarification |
Must be done by a Rimrock consultant. |
| Type |
Resco Project Settings |
| Supported |
Limited Support |
| Additional Clarification |
Must be done by a Rimrock consultant. |
Please Note: Modifying the live mobile project directly can result in downtime and lost data.
Please Note: Customers should not be using Woodford to modify their mobile configuration without approval from Rimrock.
Best Practice: Mobile adjustments should be done in a separate project and tested before being rolled out.
Business Central
| Type |
Not Supported |
Limited Support |
Fully Supported |
Additional Clarification |
| Custom Extensions |
X |
|
|
|
| Microsoft Add-ons |
|
X |
|
Situation specific, speak with Rimrock for clarification. Client would be responsible for testing in a separate environment (if Rimrock approves) and any support that might result would be fully chargeable.
|
| Third Party Add-ons |
|
X |
|
Situation specific, speak with Rimrock for clarification. Client would be responsible for testing in a separate environment (if Rimrock approves) and any support that might result would be fully chargeable.
|
| Copilot |
|
X |
|
Situation specific, speak with Rimrock for clarification.
|
| Type |
Custom Extensions |
| Supported |
Not Supported |
| Type |
Microsoft Add-ons |
| Supported |
Limited Support |
| Additional Clarification |
Situation specific, speak with Rimrock for clarification. Client would be responsible for testing in a separate environment (if Rimrock approves) and any support that might result would be fully chargeable.
|
| Type |
Third Party Add-ons |
| Supported |
Limited Support |
| Additional Clarification |
Situation specific, speak with Rimrock for clarification. Client would be responsible for testing in a separate environment (if Rimrock approves) and any support that might result would be fully chargeable.
|
| Type |
Copilot |
| Supported |
Limited Support |
| Additional Clarification |
Situation specific, speak with Rimrock for clarification.
|
Please Note: Advanced customizations can lead to support issues and extra cost on FIELDBOSS upgrades.
Best Practice: Work with a Rimrock consultant to find a way to meet your requirements without advanced customizations or to submit a product request to the Rimrock product team to have the product enhanced.