All Resco products can be utilized as standalone solutions, tailored to any industry use case. However, Resco Inspections, Routes, and Mobile CRM can also be effortlessly integrated with Microsoft Dynamics 365/CRM, Salesforce, and even other third-party backend systems. Let’s explore these options a little closer. Continue reading
How to integrate mobility into a well-run company without interfering with its existing operations?
We believe that providing tools that cover the whole lifecycle of a mobile solution simplifies the implementation, user adoption & engagement with business apps. The right set of mobile app development tools enables anyone to build apps, and beyond.
With Resco platform’s tools, you are able to: Continue reading
The alpha and omega of using CRM on the go is your data. Access to data whenever and wherever. Therefore, Resco Mobile CRM offers two types of approaches to data that can be used as needed. Continue reading
When do synchronization conflicts occur?
A synchronization conflict comes into play when a user modifies a record in the Resco Mobile CRM application, but before he synchronizes the change, this record is also altered on the CRM server. In other words – the same record gets updated both in the mobile client and on the server, but neither of these modifications has been yet synchronized between them.
And thus the conflict occurs: Which modification should be applied to the record,both in the app and on the server, after the next synchronization takes place? Continue reading
You might have encountered the following situation: You’ve created a mobile project in Woodford, but the changes are not applied to the Mobile CRM application when a user synchronizes it. So what can you do? Should the app misbehave like this? Continue reading
Offline Scenario 1
A mobile application provides an online access to CRM data. Every screen provides a button, pressing which the application makes a screenshot and saves it to the local memory of the mobile device. When the device loses an Internet connection, it provides the user a list of stored screenshots. Continue reading
In the previous post titled Mobile CRM limits. Where are they?, we talked about things that limit the application; such as RAM, storage and Internet speed. If you haven’t read that post yet, we highly advise you to do so.
What we are going to do now is to give Resco Mobile CRM application a test run and investigate the database it created.
Desktop is the best platform for such experiments – all the tools are available for free and the file system is open. (Plus, there’s a security benefit: Your business data won’t be exposed to the public network.) Continue reading
While desktop Dynamics CRM installations make use of fast machines with (nearly) unlimited storage, mobile devices are severely limited in this respect.
You typically get numbers such as:
- RAM Memory: ~1GB RAM (iPhone5/6, high end Android devices approach 3GB).
Low RAM values (~500MB or less) will negatively impact the database speed or, for example, the download speed.*)
- Storage memory: It’s here where the database will be located.**) Today’s mobile devices typically offer 4+ GB of storage memory, which is – by proper planning – enough. We’ll return to the subject later.
- Speed: It is difficult to bring any generally applicable numbers. Instead, here are a few numbers that measure activities done by Resco MCRM:
Database writes on a decent mobile device are 5-10x slower than the same operations done on a rather aging 2GHz W7 desktop. And it can go even worse, for example Xml parsing (used in communication with CRM server) is ~100x slower.***)
- Internet speed: We cannot give any generally applicable statements here. Speed of 3G networks vary between 144kbps to 4+Mbps, 4G networks are even faster.****)
“I see fields as “Unknown” when in the offline mode. Why is this? And how can I correct this?”
Unknown means that the information is not available in the offline mode; i.e. records are not stored in the local database of the phone/tablet. Continue reading
Synchronization filters are usually the tools of choice to limit the amount of records pulled down to a mobile device during synchronization.
While they work perfectly during the full synchronization, there are some scenarios where they might not work as expected during incremental sync. Continue reading