If you connect an Excel pivot table to anlysis services, the Dimension in the field list show all their available attributes (that then can be pulled into the pivot). Our client wants these attribute names to appear in the selection list in a predefined ordering (not alphabetical). How can this be achieved ?
The short answer is: You cannot.
But what you can do is using display folders: For each attribute, you can define the "AttributeHierarchyDisplayFolder" hierarchy, for user hierarchies, the property is just called "DisplayFolder": You can enter any text for this property. Then, Excel displays the attributes/hierarchies within folders as configured. The folders are sorted alphabetically within the dimension, and the attributes/hierarchies are sorted alphabetically within the folders again. But by defining appropriate folder names, you can influence the display order at least partly.
Related
I am trying to create a categorized view of all Notes documents that have a field with exact same value, i.e. there is a field for Contractor Name and I want to create a view that lists each Contractor and the documents that relevant to each. How do I do this? I have tried view formulas like the following but no success as yet
SELECT #IsAvailable(Contractorid) & #Count(Contractorid) > 1
SELECT #Count(#IsAvailable(Contractorid)) >1
Nsf databases are no relational databases. The count of different documents with a unique value in a specific field cannot be used to build a view selection formula.
You could write an agent, that runs through all documents and counts them and puts all with count > 1 in a folder, but this is quite a lot of LotusScript code and needs some advanced knowledge.
The other possibilit would be to categorize the view by ContractorId and add one column before that categorized column: simply use 1 as column formula and select "display totals" in the column properties as well as "hide details".
Then at least you have the information, how much documents are in each category, but unfortunately you cannot filter by it and you cannot sort by this column.
A third possibility would be to use an xpage interface, but that is even more work to do and a completely different story developmentwise.
This is similar to view to identify duplicates. My approach is to use folder.
Make a new folder with design of your view. Instead of (not working) selection formula use short LS code as an action, or QueryOpen event (make sure only one user runs the script).
The code should cooperate with another (hidden) view sorted by Contractorid. Make a ViewNavigator for that view and traverse through it with simple logic - if previous entry has the same Contractorid as the current one, put both documents into folder**. That way you will get list of all documents with duplicate Contractorid. Make sure to wipe all the current content from the folder at the start.
** This can be optimized further by slightly more complicated algorithm to handle first duplicate diferently - for more than two duplicates this algorithm makes extra calls of PutInFolder method.
I'm trying to query against a SharePoint List using KQL including some properties of that list that have a space in their names.
Example:
Src State:"WA" Prod Id:"X12" SomeFreeText PATH:http://server/sites/items/New%20Items/*
The free-text filter works as expected when alone, but returns nothing when including those property filters, such as "Src State".
I assume that is a problem with the space in the name. So, I've tried changing the space to "%20" and to "x0020" and even enclosing the property name between quotes (single and double), but not results found!
What I'm missing?
If you want to run a KQL search on list it's a little bit more complex than just using the column name. KQL is a part of Search Service and the columns have to become managed properties. Managed property names cannot contain spaces. SharePoint automatically creates managed properties from site columns, but if the column is directly added to list (and not as a site column), then you have to create managed property manually in Search Administration.
So if the columns are site columns, then there is a specific naming convention on how the managed property names are created (https://technet.microsoft.com/en-us/library/jj613136.aspx). If "Src State" and "Prod Id" columns are simple (say Text, or Choice), then the following query should work:
SrcStateOWSTEXT:"WA" ProdIdOWSTEXT:"X12" SomeFreeText PATH:http://server/sites/items/New%20Items/*
If this doesn't work - please check the Search Schema in Search Administration whether the managed properties for these columns have been created. If not, then you will have to create them manually and ReIndex/ReCrawl list content. Instructions on how to do that are here: https://technet.microsoft.com/en-us/library/jj219667.aspx
I am wondering if it is possible when I choose some item from let's say drop down menu in one place , on some other place to appear just some definite items that are preliminary identified to be related to this item. As an example, if you have a company structure- See below the picture- Subsidiary 1( Sub1) has just one Subsidiary with a code Sub1Sub1, so I will be expecting under the required place to appear (which might be in different worksheet ) just Su1Sub1, if I choose Sub2 from the main menu, I will be expecting in this place to get Sub1Sub2 and Sub2 (two different rows) , etc. Initially I was thinking to do this with multiple vlookup formula with syntaxis (iferror(index(.....),small(..)), but in this case we don't have values to bring, we have a combination of symbols (Sub1sub2) etc.. It can be done with multiple if(if(if( etc, but imagine we have many companies so it would be difficult with if(if)s..Please advise.
Use a list box element to select from your master entities.
Use the Change event of this list box to preload a second listbox for the child entities via VBA
The same can be done with the data validation items if you prefer in cell dropdowns. Then you use the worksheet_change event and check if the cell containing the master entity has changed, and if so you reload the correct set of child entities into the data validation list of the child selection field.
So - I'm making a data view that is to contain a list. This list has a field that will be used to match up against two other lists. If there is an entry for this value, it should show the value from the other list, otherwise show a link to add a new one.
So, what I need to do is make a data source consisting of the rows from list 1, and fill in the Ticket field with a value from the Tickets table matching the ID value from list 1. The same should be done for the Change Type field.
Can anyone point me in the right direction to accomplish this? I've found a few tutorials, but they seem to be for showing all the data together and not match up on any specific columns for linkage.
Thank you
What you are aiming at is not available in SharePoint out of the box.
There are two approaches you can look at:
Create your own custom lookup field template for single/multiple field
selection with some sort of field
editor. Create your own controls and
program the associated code behind
logic.
Use some existing custom solutions. One such sample is on codeplex:
SharePoint Filtered Lookup Field
I have a BIRT report in Rational Software Architect that outputs an element's name in one column. When I run the report on my whole project, I get lots of duplicate columns because I have elements with the same (unqualified) name in different packages. How can I edit the BIRT report to use the fully-qualified name?
The standard UML data sets do not have this element value we must add it from the modeling data source to the data sets you want.
In the data sets which you are reading for you report table, right click
the "data set"->edit. Select Column Mapping from the list in the Edit Data Set window that popped up. In the Browse grouping select the model dropdown button and select the uml meta-element in question. Expand the tree until you get to a list of properties/attributes and select the qualifiedName, click the > button to add the attribute it will add a column with the query #qualifiedName. Finish and enjoy.
NOTE: Some UML meta-element types do not have this attribute, if you can't refine your data set to one that does I saw this hack... adding a column called path with a query of ../#qualifiedName which got the path or parent qualifiedName as it will more than likely have one (Component, Package, etc). It worked for the Element type.