QuickCRM Mobile gives you access to SuiteCRM on your mobile, your tablet (iPhone, iPad, Android) or your laptop with QuickCRM native apps available on App Store, Google Play and Windows Store.
#1553 - Image overwritten with the one from previous record
Hi,
I think I found a bug with the handling of Photo fields. Luckily, it seems to be reproducible.
- Add photo field to Leads' views
- Go in the detail view of a Lead (let's call it L1) and snap a photo with your camera, and save. Photo is correctly saved.
- Now open a different Lead (let's call it L2) and edit the record. Change some other field, not the Photo. (in my tests, I used "assistant phone", but maybe any field will do). Save.
- Now the photo of L1 is incorrectly copied as the photo of L2, overwriting any photo it might have (this is data loss!).
- You can repeat the process with more Leads, they will get the last photo taken assigned to them when you save other fields...
SuiteCRM version: 7.8.19 QuickCRM version: Server 5.1.9.5, Android 6.4.2
- Most Recent Love from Users
Ricardo Cairello- gabriel1
- PLAN42 AB
- Ricardo Cairello
- chrisely
- ohmdrop
6 years ago
Thank you for your feedback, I have been able to reproduce that ... but that does only happen in specific conditions. As we have to publish an important bug fix today, we should be able to fix that too.
6 years ago
Hi,
Could you check version 6.4.3 on Google Play? If you don't see it in Google Play, please try again in about 30 mn. It takes some time for Google to display it in all countries.
6 years ago
Hi, I just updated QuickCRM with your new version and it solves the problem. Great!
Just a couple of quick questions: - What about updating the server module? I have 5.1.9.5, but it seems there is a version 5.3 available, where can I download it?
Thanks for your quick answers and solutions, they are much appreciated.
6 years ago
We are updating the server module to version 5.3.3 today. As I has sent you a special version, I will send you that new version by email as soon as the module will be updated on all stores.
Regarding the browser version: - We do not update it as often as the iOS/Android version as (1) it is less and less used, (2) it will probably be even less used now that we have the Windows app. - With latest version of the server module, it will be updated to version 6.0.5 - I don't understand "I can't access the left-hand sidebar". What happens?
6 years ago
What I mean is, on the Home page, it works well: I see the "hamburger menu" icon on the top-right, and I can click it to see my Recents/Favorites/etc.
But once I enter the Leads Listview that icon is invisible, I can't click it.
Now, as I am writing this, I am beginning to think this is the expected behavior, because on the Android app the same thing happens, the menu is only available from Homepage.
I guess it wouldn't hurt to show it in the other pages, also? It's quite convenient.
Anyway that's just a suggestion, the issue here is solved and you can close it. Thanks!
6 years ago
Sorry, but in this new version for some reason I can't get the "assistant_phone" field to appear in Leads module. I'm not using it for the normal purposes, I I have it customized with a different name, and the values I am showing are simple numbers like "120". This works well in SuiteCRM desktop, and worked well in QuickCRM until this last fix...
6 years ago
Sorry I can't reproduce that issue and I can't think of any change we made in latest version that would prevent that. I have been able to add that field in Views configuration. I see it in Edit View I see it in Detail View when it's not empty (when it's empty I can see the field when tapping the top Details header).
Did you change the field type in its vardefs?
6 years ago
Ah, it was empty, that's why it wasn't showing. Forgive me, I'm still learning about QuickCRM, I wasn't aware of this feature to hide empty fields (I agree it's useful!). Thanks again.
6 years ago
You can show empty fields by tapping on the Details header. You can also force empty fields to be displayed for a specific field with SetFieldHook('module', 'field','show_empty',true);