So I have a stupid question that I need help with.

I am an converted app studio user (from dev studio) but I am working with an info assist user to try and help them build a report. We frequently have reports with more than 50 records so I typically change the lines per page to show all, however I couldn't find that option in info assist. I was able to change this report in app studio but I would prefer to be able to show them how to do it through info assist to avoid having to help them change this for every report they build.

Sorry to bother you guys with what I am sure is such a simple question but I have spent 15 minutes trying to figure this out.

Thanks,

-Luke

This message has been edited. Last edited by: <Emily McAllister>,

To be honest... I don't think there is a way to do that using info assist. there are a bunch of things what you would think are simple Style Sheet options to include. But the Style Shet options feel woefully incomplete.

I think you have 2 options here...

1) create a style sheet specifically for limiting the page to 50 lines. Your user can then use that style sheet to apply the 50 lines limitation

2) show your user how to add the value through the text editor and call it a day...

I guess there is always option 3 which is put in a NFR...

Create an INCLUDE member that has:
SET LINES = 998 (this will always show all the lines with 1 TITLE line) Users can -INCLUDE this fex
Other SET commands can be added in the fex(if not set on the server):
SET ASNAMES = ON, BYDISPLAY=ON, etc
OR
ON TABLE SET LINES 998

TABLE FILE CAR
PRINT *
ON TABLE SET LINES 998
ON TABLE PCHOLD FORMAT HTML
END
-EXIT

This message has been edited. Last edited by: Tom Flynn,

Tom,

That's a good way to handle it... But how can you do that within Info Assist, which I understand to be the crux of the issue? I don't see a way to include another fex in the report builder. You can in Document... but then it forces it to be an active report, and that brings other problems with it.

I guess you could add SET LINES = 998 to the site profile and push that globally for all reports. That's one way to do it. Might not be a bad way either.

I am not an IA person, but, I have learned a bit.
Select the reporting object and click "Edit in Reporting Object Tool". Then edit "PREPROCESSING OTHER"
Then insert your INCLUDE like so -MRNOEDIT -INCLUDE common_include_folder/your_set_commands_here.fex(this is just an example).
You can also place Dialogue Manager commands in there as well; again, my understanding, have not implemented.

SET commands for a global community placed on the reporting server(edasprof.prf) is the best practice, imo...

Tom,

That's not IA, that's from app studio/dev studio. IA has a lot less functionality. Luke was asking how his users would be able to add the command. Unfortunately a user with only access to IA won't have App Studio/Dev Studio so would be unable to change reporting objects etc. But as you point out, these are all places that Luke can make the adjustment for them. Some more global then others.

eric,
When I right-click on My Content in IA, Reporting Object is available. My suggested direction may be outdated, but, the functionality is still there:

I stand corrected Tom.

I didn't realize you can get there from the web. I wouldn't have thought to use Reporting Objects in this way, considering that you would have to create a new reporting object every time you want to do something slightly different. But its definitely a way to do it, and may be the only way.

I have a workaround for this.

1. Create a report in InfoAssist, save it and close.

2. Right-click on the saved report, then "Edit With Text Editor".

3. Type "SET LINES = 998" into the first line of the FOCUS code, moving everything else down by one line. Save and close the text editor window.

4. Open the report by double-clicking on it or right-click and select "Edit". You should get a message warning that the report was edited outside of InfoAssist; confirm that you want to continue.

5. Save the report and close. The next time you open the report, there should be no warning and you should see more than 50 records.

InfoAssist will replace the "SET LINES = 998" with "ON TABLE SET LINES 998" in the "ON TABLE" section of the FOCUS code.

Squatch, wow, a GUI/Code combo TKO!

quote:

Originally posted by Francis Mariani:
Squatch, wow, a GUI/Code combo TKO!

Eye of the Tiger, man. Eye of the Tiger.

A workaround(not really, though) for those that can EDIT, most IA users can't...
If they could EDIT, this post probably wouldn't be here...

not that any one cares... but that is one of the first things I mentioned.. open with text editor and add the code.... just saying....

But thing is, we don't know whether the user even has access to edit the text. Remember that's a granted permission, as is reporting objects. Depending on the level and security settings assigned to the user, they may not be able to do either.

at the end of the day though. Info Assist should be able to handle this without having to deal with the IBI "Scare Tactics" that you might have broken the code by doing something it should be able to handle anyways. Same with sizing a column, adding borders etc. I'm pretty sure that report assistant used to be able to do a bunch of these things. As I some times feel like we have fallen backwards with IA instead of forwards.

quote:

Originally posted by eric.woerle:
not that any one cares... but that is one of the first things I mentioned.. open with text editor and add the code.... just saying....

Actually, you mentioned making the change in App Studio. That is different than editing the code within the WebFOCUS portal. Your users don't need App Studio when editing that way. In theory, it is something they can do without asking you for help. That was the problem I was trying to solve.

Also, I assumed that your users were considered developers with text edit permission. That is the way it works here.

quote:

Originally posted by Tom Flynn:
A workaround(not really, though) for those that can EDIT, most IA users can't...
If they could EDIT, this post probably wouldn't be here...

Since Luke was using App Studio to do the editing, I didn't know for sure if he was aware that editing can be done from the WebFOCUS portal (given the proper permissions). So I mentioned it.

As Luke states, we ALL know how to EDIT in App Studio.
AND, Eric never mentioned making the change in APP Studio...

Over and Out!

quote:

Originally posted by Tom Flynn:
As Luke states, we ALL know how to EDIT in App Studio.
AND, Eric never mentioned making the change in APP Studio...

Over and Out!

I was talking about editing in the WebFOCUS Portal, not App Studio.

And Luke mentioned making the change in App Studio.

Sorry guys, I shouldn't have digressed like that.

At the end of the day, I think we can all agree that IA is inadequate.