Hi Dmitrij,
Member keys must be unique within the first 113 characters, as documented here. It looks to me like the two strings in your table are the same for the first 117 characters, and I think this is why only one member is being inserted when you build your cube.
If you have long strings in your table that may not be unique within 113 characters, and want to create a member for each one, I wonder about using a hash of the string as the member key, creating a property with the text of the string, and using that property as the member name. However, you should avoid this if it would create an excessively large number of members (or if the member names would be so long that it wouldn't be practical to display them in pivots or dashboards).
Hi DJ,
Do the rows you want to print have something in common? If so (for example, if you want to print all the rows for customers in a particular city), you could add that characteristic (e.g. City) to the cube as a level if it isn't already one, and then either filter the pivot table to the City member you're interested in, or add the City level to rows/columns and select cells corresponding to the city you want to view the listing for. Then you should be able to see a listing that only has the data you're interested in, and print or export its results.
The check-boxes in the listing are mainly useful if you are working with a custom action, but that probably isn't the direction I would recommend you go if you are starting out with IRIS BI.
First of all, I'll mention the suggestion in our documentation that, "Generally, if you configure InterSystems to allow unauthenticated access [i.e. UnknownUser], it is recommended there be unauthenticated access exclusively." That is, trying to manage security for UnknownUser isn't necessarily recommended.
The documentation on granting SQL privileges on specific columns (properties) is here. I don't know enough about your situation to feel confident about whether that is what's going on, though. You can also enable auditing for %System/%SQL/PrivilegeFailure to see if that gives you more information. Feel free to open a WRC issue if you are having trouble with this.