Focal Point
[CLOSED] Can't Edit anymore

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/3437070726/m/7537037096

August 31, 2018, 03:26 AM
jenni
[CLOSED] Can't Edit anymore
Hi,
it happens sometimes, that I can't edit my Report anymore.

There is nothing Special in my code,
so I don't know why it happends sometimes

This message has been edited. Last edited by: FP Mod Chuck,


WebFOCUS 8.1.05
Windows, All Outputs
August 31, 2018, 04:34 AM
jenni
It means I can't click the edit button, because there is None.


WebFOCUS 8.1.05
Windows, All Outputs
August 31, 2018, 08:54 AM
Mike Williams
Did you make any edits via the source? I've found that after any text edits I would need to immediately open the report in the GUI and save it. Otherwise, I'd find that the option to edit would no longer be available.


WF Version 8105
August 31, 2018, 03:36 PM
FP Mod Chuck
Jenni

Better open a case and report this to techsupport.


Thank you for using Focal Point!

Chuck Wolff - Focal Point Moderator
WebFOCUS 7x and 8x, Windows, Linux All output Formats
September 10, 2018, 10:31 AM
Doug
I have a similar issue in 8202m Gen 60.

So, I'm looking forward to the solution.




   In FOCUS Since 1983 ~ from FOCUS to WebFOCUS.
   Current: WebFOCUS Administrator at FIS Worldpay | 8204, 8206
September 26, 2018, 06:24 PM
CoolGuy
There's an issue/bug with the role privilege for allowing others to edit via Reporting Objects in IA+ in 8202M that has been present for I'm not sure how many releases. If you no longer see the option to edit in the new WF Home UI, try editing from the Legacy Home page instead. It should be present there at least if your issue is this issue. That's the workaround we've been utilizing.

Another issue with IA+ is that if your using a filter clause created with the Expression Builder feature, depending on what you put in there, it can bork your ability to edit/open the report/chart/etc. Also, creating DEFINE/COMPUTE fields sometimes kill it as well.

Mike mentioned the editing the source manually bug already.

I could go on, but most likely you'll need to determine whether it's viable and desirable to upgrade out of the issue. Case workers love to ask if we have upgraded after the 1-4 months of not responding back to us happens, finally chiming back in asking such after the 1 initial attempt of resolving the issue ends up at the "Please give us all your log files and stack traces and we'll get back to you..." response. Then, if you do upgrade, you welcome 12 new bugs even though the one is fixed, if you're lucky.


8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.