LBI rollout to Power Designers

Sort:
You are not authorized to post a reply.
Author
Messages
mark.cook
Veteran Member
Posts: 444
Veteran Member

    We are in the process of completing our LBI dev server with the intent of allowing a small group of power designers to build reports, SN, Dashboards in DEV. If you have rolled this out to a group like this, other than a standard promotion process, what are the big gotcha's that you can share.

    Milo Tsukroff
    Veteran Member
    Posts: 47
    Veteran Member
      Several things that we did 'right' that have helped us:

      - Set up access to a single area (For instance, a share drive) under which all published Crystal Reports reports are stored. We made folders for working reports of various kinds, and another folder for "Source" reports under which were folders for each type of report. This is not the Repository, just a working area that allows everyone to access all Crystal Reports reports once they're published on the system. When creating a modification, it's easy to locate the current version of the report, go off into another folder to work on it, then bring back the 'new' report and publish from there.

      - Allowed access over the network to the Repository. This was very helpful because we could see what was actually out there. Plus, when there were problems with reports not scheduling the way we thought they should, we could see that. Finally, if for some reason the Crystal Report published in LBI was not where it should have been in our storage area, we could grab it from the Repository and bring a copy back for proper storage.

      - We put all power users in the same LBI Role (LSA Group). Then, every time we published a report, we gave rights to that LBI Role so that other users could see the reports. Failure to do this leads to questions like, "Did you publish that report? I don't see it!" Security keeps even power users from seeing reports they don't have access to.

      Hope this helps.

      You are not authorized to post a reply.