Dear visitor, despite the COVID-19 outbreak, our team continues operating at full speed.

Also, here is the form where you can apply for a special discount and we will contact you with possible options. Stay safe and continue achieving your business goals.

Fill the form
Get Free Trial
Get Free Trial

Copying via keyboard shortcut no longer possible with v. 2.8.9

Answered
Lee-ann Dunton asked on June 26, 2020

Hi there,
Our users are complaining that they can no longer copy & paste values from a FlexMonster report using “command + C” on their keyboard (on any browser).
This has only been an issue since we upgraded to the June 2020 instance (v. 2.8.9) [build 06/23/2020 04:33:55]. I believe we were previously on v. 2.8.4 prior to this upgrade, and this functionality was still available.
They keyboard shortcut (“command + C” on a Mac or “Ctrl + C” on a PC) has always been used because the right click menu doesn’t contain a “Copy” option. Now, in order to copy any given field, the report first has to be exported to either Excel or CSV. This is obviously very time consuming and especially frustrating when they’ve previously had that much-faster option.
Was this functionality removed on purpose or for a specific reason? Is there any chance of getting it added back in the next release? This functionality was used by our teams constantly, and taking away this functionality has caused a lot of frustration.
Please advise! Many thanks,
Lee-ann

2 answers

Public
Lee-ann Dunton June 26, 2020

As I posted this question I saw this update on the following ticket: https://www.flexmonster.com/question/ctrl-c-does-not-work/

Illia Yatsyshyn  Flexmonster ⋅ 2 days ago

Hello, Sergii,
 
Thank you for writing to us.
 
This issue has already been reported and we are currently working on the fix. We are going to return to you with updates on this ETA Jul 14th.
 
Please let us know if you have any other questions we can help you with in the meantime.
 
Regards,
Illia

Public
Mykhailo Halaida Mykhailo Halaida Flexmonster June 30, 2020

Hi Lee-ann,
 
Thank you for writing to us.
 
Yes, as you’ve already pointed out, the mentioned bug is currently being investigated and is going to be fixed in our upcoming release ETA Jul 14th – we will make sure to reach out to you with a reminder.
 
Please let us know if you have any other questions we can help you with in the meantime.
 
Best regards,
Mykhailo

Please login or Register to Submit Answer