FAQ: Custom Development, Development Requests and Missing fields/features

Q: It seems CRM for Outlook is missing a feature I need that the normal B1 Client can do. What to do?
A: The CRM for Outlook screens that mimic SAP Functionality will always be a subset of the B1 Client Functionality. There are 3 reasons for this:
1. The goal of the product is to offer a more streamlined version of the SAP Screens with the most common fields (it has never been the intention to 100% mimick SAP Screens)
2. Sometimes features come in a new version of SAP that introduces new fields and functions. The product however always try to support the last 2-3 releases so a brand new feature can't always be added as soon as SAP offers it as this would break backward compatibility
3. Sometimes a feature in the B1 Client is not exposed in the SAP SDK so it is not possible to support it.

Q: What should I do if some feature I need is missing?
A: Please post it in the community section of the help-center (https://support.boyum-it.com/hc/en-us/community/topics/200115256-B1-CRM-for-Outlook-Feature-Requests). We are then notified of the missing feature if:
1. It gets enough votes and makes sense for the product
2. If it is a high-value feature/bug that does not break backward compatibility

Q: If I ask for the feature, when will it be included in the product?
A: There is no single answer to this as it can only be evaluated on a case by case basis. So it might be the next release, it might be in years or in some cases it might never happen 

Q: Do you accept custom development jobs (aka can I pay you to add the feature I need)?
A: While we did this in the past, we have recently decided not to do any sort of custom development anymore as it does not follow the strategy of a standard product.

Q: That's dumb! Don't you want my money?
A: While it might sound counter-intuitive, as a high-volume general product, custom development is a bad practice: 
1. Our main goal is to offer what gives more value to the most customers and custom development tend to be used by only a few and increase the overall complexity of the product.
2. It is not really fair to take away resources from the overall product and the most requested  features (that all the customers on maintenance are paying for in terms of maintenance)
3. It is not common practice for standard products - Example: You can't contact a company like Microsoft or Apple and have them change a feature in Windows/iOS (but you see that if enough people ask for a feature they might add it).