MicroStrategy Mobile Design and Administration Guide

More documents

Recommendations

Info

2 Designing Reports and Documents for a BlackBerry Mobile Design and Administration Guide Best practices for designing Mobile-friendly documents If you are designing a document in MicroStrategy Desktop or MicroStrategy Web for use on a BlackBerry, consider the following best practices: • Refer to Best practices for designing Mobile-friendly reports, page 108 for suggestions on designing each report within the document. • Limit the number of Grid/Graphs included in the document. Each Grid/ Graph in a MicroStrategy document is displayed as a separate tab when the document is displayed on the mobile device. At least one Grid/Graph must be included in the document for the document to display any data in MicroStrategy Mobile. • The names of the tabs above a document are determined by the names of the Grid/Graphs in the document. You can specify the name of a Grid/ Graph in the Title field in the Properties dialog box in MicroStrategy Desktop or MicroStrategy Web. If you do not specify a title, the generic name of the Grid/Graph is displayed. • Grid/Graphs are the only controls on documents that are displayed in MicroStrategy Mobile. Selectors, panel stacks, widgets, lines, rectangles, and text fields are not displayed in MicroStrategy Mobile. Avoid including these types of controls on a document that will be used on a mobile device. • To include graphs in documents, you must design the report in original layout data view. Original layout data view disables some Mobile features. For details about the different data views, see Selecting a data view for a report or document, page 111. • Do not subscribe to an HTML document for use with MicroStrategy Mobile. HTML documents are not displayed in MicroStrategy Mobile. For details to design documents in MicroStrategy Desktop, see the MicroStrategy Report Services Document Creation Guide. For information on designing a document in MicroStrategy Web, see the MicroStrategy Web online help. 110 Best practices for designing Mobile-friendly documents © 2012 MicroStrategy, Inc.
Mobile Design and Administration Guide Designing Reports and Documents for a BlackBerry 2 Selecting a data view for a report or document Reports and documents that are designed to be viewed in a mobile device must have a data view assigned to them: tabular interactive or original layout. Each of these data views has its own benefits but also disables some features: • Tabular interactive data view allows the widest number of report and document manipulations on the mobile device, but does not allow certain report formatting during the design process. See Tabular interactive data view, page 111 for details. • Original layout data view provides flexibility in the design of reports and documents, but disables some of the Mobile user’s functionality. See Original layout data view, page 112 for details. The report designer designates the data view for each report when the report is designed in MicroStrategy Web or Desktop. The data view cannot be altered remotely using a mobile device. When designing a report or document for a Mobile user, it is important to think about the way the user will interact with it. If the user will benefit from a simple grid layout and the ability to rearrange the data on the report, tabular interactive data view is the best choice. If the report is best understood with minimal manipulations, but requires a more complex layout, original layout data view is more appropriate. For steps to set the data view when designing a report for Mobile, see the Report Options dialog box section under Grid Formatting in the MicroStrategy Web online help. Tabular interactive data view Tabular interactive data view allows the MicroStrategy Mobile user to use all functionality available to work with the reports and documents on the mobile device. The full functionality described in the MicroStrategy Mobile Analysis Guide is available to the user in tabular interactive data view. However, this data view restricts the report or document designer from some design features, as described below: • Placing attributes in columns: Any attributes placed in the columns of a grid will be moved to the rows of the grid when the report is delivered to the device. © 2012 MicroStrategy, Inc. Selecting a data view for a report or document 111
Page 1 and 2:
MicroStrategy Mobile Design and Adm
Page 3:
International Components for Unicod
Page 6 and 7:
Contents Mobile Design and Administ
Page 8 and 9:
Contents Mobile Design and Administ
Page 10 and 11:
Book Overview and Other Resources M
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
1 Designing Reports and Documents f
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89: 1 Designing Reports and Documents f
Page 142 and 143: 3 Administering MicroStrategy Mobil
Page 188 and 189:
3 Administering MicroStrategy Mobil
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Glossary Mobile Design and Administ
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Index Mobile Design and Administrat
Page 240 and 241:
Page 242 and 243:
Page 244:
show all

MicroStrategy Mobile Design and Administration Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?