I'm working in Cognos 8, and I have the first three fields in a report:
Agency
Org
Name
I'm displaying Agency and Name always... Org is displayed based on a Render Variable. So on the prompt page, if the user selects yes, display Org, it's displayed on the report. If they select no, it's not displayed.
The sort order needs to be Agency, Org, Name.... however, if Org does not show, I need the sort order to be Agency, Name.
However, even when the Org is not rendered, it's not sorting Agency, Name. it's still sorting with Org in there.
How can I force it to not sort by Org if Org isn't rendered?
Thanks
Personally when using render variable, I prefer to use blocks.
So, in your case it means you should create two blocks and then put a list in each block.
The data source of the list can be identical, but the sorting is different:
Related
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.
I have a View in Lotus notes by formula.
The View is as follows by Org Exec \ Organization \ Total Headcount
I have a "show twistie when row is expandable" enabled and "Categorized" selected as Type for the column "Org Exec" & "Organization"
For example data looks like this: Marshell Rodrigues \ Tester \ 100
However my problem is that tester has the list of 100 people within it and i do not want to show that level of details in the view? I want Organization not to show the list of people within it.
I tried the Hide detail row on the Organization column properties but that does not work it still shows data within the organisation in the view
any ideas or suggestion ?
What is the purpose of the view?
I am trying to Export this View in Excel Using ODBC Connection Thus i want the details at a higher level
What kind of documents are in the database?
Each employee has his record in the database with his details liek organization , execs, headcount name, serial number .
What kind of information should be displayed ?
Like i said the information to be displayed need to be at a high level for example :
Give me All Organization Execs by Organization Total Headcount (i just want the total number i do not want to see a drill down on thoes numbers in the view)
Example if Org "abc" has 10 headcount i just want it to display 10 ... i do not want to see who thoes 10 people are.
and from which docs does the info come from?
All the docs have a fields named Org Execs and Organisation and Headcount(were Headcoutn can be 1 if working and 0 if not working for individual month)
What are the column formulas?
Select form = "xyz" ....
Columns Org Execs \ Organization \ HeadCount (All 3 are fields in each record)
I would call that a "roll-up report", but views in Lotus Notes are not reports. They are designed to give users access to documents. Summarizing data (with totals, percentages, etc.) is just an additional feature that was thrown in on top of the functionality for accessing documents.
There are a variety of reporting products for Notes, and they are designed to do what you want. You might want to look into them if you have a lot of similar requirements for a lot of different views.
There is also a way that you could do this with ReaderNames fields and an ID file that does have access to the database but doesn't have access to the documents. Categories that are "empty" (i.e., contain no documents) will show up for a user, but this is a hack and not the right way to approach the problem. I really do not recommend it. (It will probably only work for viewing anyhow. I doubt an export will actually work in this setup, though I confess I've never tried it, and maybe it will.)
If this is just a one-off job, my suggestion would be to write an agent to collect the summary information that you want and either create summary documents in a folder, which you could then export and delete; or to have your agent directly write the data to Excel.
What I am doing might be really stupid, if so, please correct me, but I am trying to do the following thing:
I want to have a list with (for example) the following items:
List Addresses
-Name
-Address
-City
-Country
But, based on their Country, I want to display different columns that I want to record in a List. For instance:
CountryColumns
(United States - SSN - Yes)
(United States - State - Yes)
(United States - Province - No)
(United Kingdom - SSN - No)
(United Kingdom - State - No)
(United Kingdom - Province - Yes)
And then when the user picks United States in the country list, the next time the user edits his information, certain columns will be shown. (It's also possible that all will be shown, and that the next time the columns with No will be hidden).
I've looked at ways to do this, and I only found out that Infopath is able to do this. But, that'd mean I would have to create a different view for every country, and show / hide certain columns. It seems like that is a bit of overkill.
Anyone knows a way how to do this?
Greetings,
Mats
Here are three options:
Custom content types. This is probably the most SharePoint-y way to do it. You can create a content type for each Country and then control which fields are included in that content type. The obvious downsides to this are that you could end up creating a lot of content types and also that selecting a content type (especially when creating a new item) is not the same as selecting a choice from a dropdown list.
Javascript/jQuery. Either by changing your master page or by adding a Content Editor Web Part to your Edit Form, you could use javascript to hide certain fields based on the selected value of Country.
Custom fields. This is the most involved, but instead of having the SSN field be a regular Single Line of Text field, you could create a custom field that inherits from SPFieldText and then manages its render visibility based on the selected value of Country.
There are four ways you could modify SharePoint to do this that come to mind.
Have a list address content type and then a separate content type for each country that requires extra fields. Use a webpart to enter data to the list using the correct country's content type.
Same as above but instead of entering data through a web part, you can add the data into the list using the base address content type. Use an item adding event receiver to decide which content type to add the data to.
Use one super content type that includes all fields but with custom list view pages to filter the fields based on the county value.
Use infopath with either separate views for each country or a section for each special field with a condition to hide it if the required country isn't selected.
Personally I would recommend 4. It's the simplest and quickest to implement.
You cannot do this out of the box.
I got a question about the behavior of lookup fields when importing data. I wonder how the lookup fields behave when the list they point to is being replaced/imported. To explain the issue, I will provide a quick example below:
As example, assume we have these two sharepoint lists:
Product Types
-------------
+ Type Name
+ Code Nr
+ etc
Products
--------
+ Product Name
+ Product Type (Lookup field to list "Product Types")
+ etc
In my scenario, the Products List contains production data on the production Sharepoint platform. It is filled with data by the business users.
However the Product Types list contains rather static data and is maintained by the developer.
Now after a development cycle, the developer wants to deploy his new webparts and his new data (product types list). The developer performs the following procedure:
On the dev machine: Export "product type" list using stsadm
On the production machine: Delete all items in the "product type" list
On the production machine: Import the "product type" list using stsadm
This means we basically replace the "product type" list on the production server while keeping the "product" list as it is.
Now the question:
Is this safe? Will the lookup references break under certain circumstances?
Any downside of this import/export procedure?
What happens if someone accesses a "product" during the import? Will the (now invalid) reference clear its own content (become a null value).
What happens if the schema of the "product type" list changes (new column)? Will this cause any troubles?
Thanks for all feedback and suggestions!
Update 1
The imported "product type" items have the same IDs as previously deleted ones.
Update 2
Started a bounty to get some more feedback/opinions.
We have had this exact same scenario before. This is a little tricky, depending upon how you will approach it.
1) Delete and Recreate Product Type list through UI
If you delete and recreate the lookup List(Product Type in your case) through UI, then you will lose the connections because the List's id GUID will change upon recreation. So do not go that route.
2) Delete and Recreate Product Type through a Feature
If you had created the Product Type list through a feature.xml file using the <ListInstance> element, then if you delete that list and then recreate it using the same feature (basically Id attribute of ListInstance remains the same, number of list items, i.e. the number of <Row> elements, may change), the association would be maintained. So if you were adding 5 more product types, then if you had created the list using a feature, you could just delete the list and provision the new one using the same feature with extra info for new items and everything would just work!
As a side note, this is the better approach because if you have to do the upgrade on a lot of servers, then rather than doing list export import via stsadm, feature deactivation and activation is a much more recommended solution. This is how we did it.
3)Deleting all list items from Product Type and adding new ones (list is never deleted)
If you are linking the lookup field (in Product List) to the ID field of the lookup list(Product Type), you have to remember that ID is auto-incrementing, so if you delete all items and then add new ones, then their ID's would be different. Say you had 5 items with ID's (ID field is not shown in UI while editing in Datasheet view) 1-5 in the list. If you delete them and add new items, their ID's would start from 6 and not 1 again. So if your lookup field had link to the item with ID 1 in it, then this method is not going to work because there is no item with ID 1 in the Product Type list anymore. So you might want to really try this out before going to production with this method.
4) Editing the list in place
If the list is not extraordinarily huge, and you only have to make this change to one or two instances, could you not just edit the list directly in the datasheet view on the prod server? When editing in datasheet view, do not delete the item, but just overwrite the values of its columns. And you can add more items if you want. This will make sure your ID's are valid.
I have mostly talked about adding new items to the list. Now if you were deleting existing items, then your lookup fields will be affected because assuming you linked the field by ID, the ID is not present anymore since the item has been deleted. Basically, any method you use, maintaining your ID's is critical.
Now regarding your doubts/questions:
I am not too sure about stsadm export import for a list (never done it myself), but stsadm can be tricky as some operations will work on certain scopes only. So you better try out your exact scenario on a dev env.
What happens during an import is tricky again depending on the exact timing. I am sure SP has its own concurrency mechanisms, but you cannot have a definitive answer as it might probably be different based on the stage of the import. If possible, recommended approach is to do the import during a planned downtime.
Regarding changing schema of the list, a change in the schema of a list will not affect the existing list instances (for the most part). If you do this through UI, I believe SP makes changes to the content DB directly. I am not certain how you intend to do this, but if you were to add a column to an existing list using a feature, the way to do this is during feature activation by adding a new content type to the list and adding your new column to this content type. This way you add the column but do not affect the existing list items.
Good luck...
There are two components to a particular lookup: the field, and the field value. The field value only contains the ID of the item(s) it refers to, and the display field. This information is meaningless without the field, which specifies what list to look at and what field to use as the display field.
The primary reason that a Lookup will break occurs on the field scope: either the list it referred to no longer exists, or the list does not contain the required field. These would generally happen if you deleted and recreated the list, but you aren't doing that. If you do break a lookup's list reference, then the only thing you can do is re-create the lookup, because you cannot configure the list reference for a lookup field once it is created.
The downside of your import/export procedure is that you lose the validity of all currently existing lookup values. A lookup maintains its integrity based on the ID of the item it references. So when the display field changes, it still refers to the same item. If you delete the item, then the lookup no longer references it, even if you create a new item that has the same value for the display field. So you would have to reassign all of the products to the new product types.
It should be noted that if you were to revert the deletion of that item, it would return to being on the lookup! The reference to that ID is kept until the actual lookup value is updated (such as by editing the Product).
All of your now invalid references will be null for purposes of interaction. You won't see anything on display forms, and you won't have the options when you try to update the product. When you do update the product, you update it to what you just set it to, which since you can't set the non-existent IDs, means that there are no more references to those IDs.
Any changes to the Product Type list's schema that do not affect the display field specified for the lookup will not have any effect on the lookup integrity. If you do change the display field in any fashion, and of course if you delete it, then it will break in the same fashion as with the list reference. However, you can set the display field, both in the UI and in the object model, so it is easy to fix this.
I have a Person field in my custom list. I want to have a view that will show multiple fields from that Person instead of the one I had to choose when creating the Person column.
So basically I want to have one column for Person and then in the view see Name, title, email, phone. All of those are valid choices but I can only pick one right now.
I really want to avoid typing in the username lookup for each column I choose to display.
This is SP 2007
It sounds like you need to create a custom fieldtype (with a fieldcontrol) that inherits from the userfield but in viewmode renders out the different columns you need. Is that something along the lines you are looking for?
http://www.sharepointblogs.com/nicksevens/archive/2007/08/31/create-custom-field-types-for-sharepoint.aspx
Note: This link is broken
You probably want a Computed Field. Note that this is not a Calculated Column. A Computed Field is what is used to display the same data is different ways. In SharePoint there is a Title field, but there is also a "Title (linked to item with edit menu)" computed field as well as a "Title (linked to item)" computed field.
See midway down this link for more details. I'm not sure if it will have all of the power that you need, but if it does it is almost certainly what you are looking for if you don't mind getting into the Schema XML file a little.
Could you use a DataView web part for this? If it's just a question of viewing the data that might be suitable.
Came across this thread and thought I'd add a tip. This suggestion is clearly not for every use case, but may work well in situations where you're managing a list rather than allowing manual inputs (verified to work with SP 2013):
Create a spreadsheet with columns to match your SharePoint list that contains multiple profile fields. (for example: name, phone number, email address)
In the spreadsheet, enter the same email address in all of the person/group field types in that row. (e.g., boss#company.com, boss#company.com, boss#company.com)
Select and copy the row(s) you wish to transfer to SharePoint.
In SharePoint, change the list view to "Quick Edit" and paste the row(s) into the grid.
SharePoint will process each field and convert the email address to the profile value you selected during the list setup.