Search results for query: *

Open Object Manager, open a project, select Tools -> Find Unused Objects.

Make sure that only authenticated users have access to Admin.aspx and anonymous users are not listed under the File Security tab in IIS. Reboot IIS. If you're still having problems, you'll have to post screenshots of the IIS pane and the File Security tab settings. This problem is something...

I assume you're using 7.5.x Web on Windows, which is a straight ASP.NET application hosted on IIS. TN5600-75x-1091 will give you the details on how to set up security (specifically, you want to change permissions on Admin.aspx.)

Read the SDK documentation for 'Portal Integration Kit'. That'll get you on your way. I strong suggest using the IFRAME Implementation (Type A).

hey spod, "MicroStrategy Intelligence Server (Windows) version [7.5.2] is interoperable with MicroStrategy clients versions 7.2.3 or higher." (from readme) I should have been more specific though -- this only applies to IS Windows. IS Universal doesn't offer legacy comp.

how would you define the security filter?

No. The other way around would be fine. For more information read "Compatibility and Interoperability" under the General Information section from the MSTR 7.5.x readme (C:\Program Files\Common Files\MicroStrategy\readme7.htm)

You would still need to use the External Security Mechanism (in the SDK) and do some java coding, or pass user/pass via URL API within the IFRAME. The process is not magic -- the login credentials need to be passed to Intelligence Server somehow, whether it's through user interaction or through...

you can't integrate reports into a portal without somehow authenticating against Intelligence Server; either way you will need to configure an MSTR user to run the reports. I suggest reading the "Using URL API to Display MicroStrategy Content in the Portal Page" help page in the SDK. in this...

The easiest way is just to use an IFRAME to display a MSTR Web page into the portal. If you absolutely can't use Web, you'll have to do some Java coding. What portal server are you using?

Desktop -> Schema -> Export Project Schema. Check 'Attribute Definitions' and 'Table Catalog - Logical View'. You will need to reconcile the two sheets. You can also pull what you need from the metadata DB tables (DSSMDOBJINFO/DSSMDOBJDEPN) using SQL.

why don't you just use a dynamic date filter?

There's no easy way to do this. You can either put a client-side redirect in the logout ASPX file so that the client is redirected upon load of the logout page (JavaScript), or make changes to the server-side logout event handler (Java). Option 1 is easier and doesn't involve the SDK. Option 2...

You might want to read technotes TN5200-7X0-0086 and TN5700-7XX-0997 to see if either one addresses what you're trying to do. A combination of these two usually solves most of the special case issues I've encountered. Otherwise, you will need to do some hacking with the Web SDK, which opens up...

You need to make an edit to PageConfig.xml. The file is in your \Web ASPx\WEB-INF\xml directory. You want the Report Execution node, so search for: <page desc="Report Execution" desc-id="" feature-id="" login-required="true" name="report" persist-mode="8" track="true"> Once you're inside that...

Try replacing your elements prompt with a date value prompt. SQL generated by prompts differ based on the prompt type. See technote TN5200-7X0-0100.