I have an issue with a lotus notes view. This view displays entries based on the number of problems in the field "All problems". This field is a multivalued field. In the view column properties for the column "problem", the multivalue separator is New line & under the sorting tab, the checkbox against "show multiple values as separate entries" is checked. When i see the view from my machine, multiple values appear as a separate entry. When i checked in another machine, the view was displayed as expected. The problem came, when i tried to do a search for documents based on a value. Now the multiple values come as a single entry which is not supposed to happen. The strange thing is it appears fine in my machine. But when i tried it in another machine, i face the issue. To make sure its not a version problem i checked it in a machine with the same version as mine(8.5.3) also tried in a lower version(7.5) but got the same result. I even tried the following: 1.delete the cache.ndk. 2. remove the DB icon from workspace and reopen the database from applications. 3. go to (Byurl) view in bookmark.nsf and delete all the documents and reopen lotus notes. 4.rebuild views using Ctrl+Shift+F9. Could not do a database rebuild(no access). Does any one know what can be the problem and possible resolutions?
The search is returning a single document, which is correct. It's the representation of the document that is annoying you, you want to have it displayed as it was originally, i.e. with a categorized column. If you are sorting another column in the view, the categorized column gets turned off.
Have a look in Search in View/More/Sort Results by, that might be your problem.
Related
I have been using PowerApps for a couple of years now to create simple user interfaces with SharePoint lists as the database.
Since last week I have started to experience a number of issues with my apps. For example, when referencing a SharePoint list single line of text column by its field name, PowerApps says that it doesn't recognise the identifier. I use the exact same formula for a different single line of text column in the same database and it works fine.
I have a gallery that I have added a couple of extra label fields to. The formula that I am using is simply 'ThisItem.ColumnName'. For one that works this is 'ThisItem.Address' and this displays the address which comes from a single line of text column. One that doesn't work is 'ThisItem.Industry'. The internal field name for the column is definitely Industry and it is definitely also a single line of text column. In the label itself I have switched between both formulas and again the Address column displays fine but the Industry column is not recognised.
I have further tried:
Recreating the database from scratch
Deleting the column/s that aren't being recognised and recreating them
Refreshing the data connections, including deleting and re-adding
Using Edge instead of Chrome
Creating a database on a different teamsite (same site collection tho)
Turning off all experimental features in the settings
I would upload some screenshots but as this is my first post, I'm not allowed to....
Has anyone else experienced anything similar? Anyone able to provide some insight as to why this has suddenly started occurring? HELP, anyone????
Thanks in advance.
Shannon
So i found what was causing the issue, still in the dark as to why though.
The gallery is linked to multiple databases (sharePoint lists) through an IF statement. The user selects a district from a drop down box and depending on what they select, the gallery is filtered using this IF statement.
The weird thing is, that the filter on the gallery works perfectly fine and displays all the records from that database. But for some reason, it only chooses to recognise a select few of the columns within that database.
When i removed the IF statement and just linked up one database, it works perfectly fine and all columns are recognised and display fine.
So, back to the drawing board on this one. At least i know now that i need to rework my gallery set up and that it isn't a case of corruption with the app or the database (that was my biggest fear!)
Hope this info provides some help if anyone else experiences this same issue.
I have a calculated column in SharePoint On-Premises that shows the number of days till a due date which works perfectly for a day or so then stops calculating, but if I go to the list settings and click the column and click ok then it calculates again?
Has anyone experienced an issue similar to this. I had this issue in both 2013 but within a few weeks moved to 2016 and still the same issue.
I've tried " " blank and also "" empty so not sure if that is causing the issue??
Is it a problem with the formula?
Here is the formula:
=IF(ISBLANK([Due Date])," ",
IF(ISERROR(DATEDIF(NOW(),[Due Date],"d"))," ",DATEDIF(NOW(),[Due Date],"d")))
Calculated columns cannot contain volatile functions, which includes those that depend on the current date.
The values in SharePoint columns--even in calculated columns--are stored in SharePoint's underlying SQL Server database.
The calculations in calculated columns are not performed upon page load; rather, they are recalculated only whenever an item is changed (in which case the formula is recalculated just for that specific item), or whenever the column formula is changed (in which case the formula is recalculated for all items).
If you need to show a dynamic value that changes with the passage of time, you have a few alternatives.
Client-Side Rendering
Consider using client-side rendering which lets you use JavaScript to dynamically determine how records in a list view are displayed. This JavaScript runs upon page load, so it can handle current time-dependent values much better than a calculated column.
To use client-side rendering, you create a JavaScript file that controls how the view displays. You upload that file to somewhere on SharePoint where people will have at least Read access to it, then edit the list view web part that you want to display differently and set its "JSLink" property to point to your JavaScript file.
Check out this answer for an example of using a JSLink file to spoof a dynamic date field.
Microsoft also provides some documentation here but I think they do more work than is necessary (creating an entire new list definition project in Visual Studio for their example instead of just creating a JSLink JavaScript file for an existing list).
Other Options
A few other options are mentioned in the older question linked above:
Conditional Formatting: You can apply conditional formatting to highlight records that meet certain criteria. This can be done using SharePoint Designer or HTML/JavaScript.
Filtered List views: Since views of lists are queried and generated in real time, you can use volatile values in list view filters. You can set up a list view web part that only shows items where Created is equal to [Today]. Since you can place multiple list view web parts on one page, you could have one section for today's items, and another web part for all the other items, giving you a visual separation.
A workflow, timer job, or scheduled task: You can use a repeating process to set the value of a normal (non-calculated) column on a daily basis. You need to be careful with this approach to ensure good performance; you wouldn't want it to query for and update every item in the list if the list has surpassed the list view threshold, for example.
To expand on the Filtered List Views option, you can have a view that shows only items that are due within a certain number of days. For example, you can display all the items due within 7 days by filtering where the Due Date field is less than [Today]+7 and Due Date is greater than or equal to [Today]. You could also sort the view to show the items with earlier due dates closer to the top.
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 am retrieving a list of values from a sharepoint list, which works well but my problem is that it only retrieves the first 100 records. there are currently 500 records that should be available.
Scenario: I have two comboboxes on an infopath form:
A List of Locations
A list of areas within the locations
the list of locations will filter the list of areas but as infopath seems to only retrieve the first 100 records so most of the locations do not show any areas as there is nothing to filter.
By design, the query will only return the first page of results from the default view for the list. Change the item limit for the default view in SharePoint, and you'll change the returned values for InfoPath.
EDIT (links from my comments, here for greater readability):
Here are sources describing this fix in MSDN forum (scroll to the bottom), a blog comment that describes the SharePoint setting step-by-step, one with a screen cap of the somewhat counter-intuitive interface, and another describing performance implications on the server side.
Hope this helps.
Just documenting what I have discovered trying to resolve the problem. I have not been able to change the default view as yet as I dont have the permission to. That should change though.
One possible workaround I have found is that you can export the list to Excel which contains all the data that I was looking for. the file that sharepoint produces is an Excel Query file like "export.iqy". You can save and open the file in notepad. which will look something like the following
WEB
1
http://SharepointSite/_vti_bin/owssvr.dll?XMLDATA=1&List={14C4ED2B-3050-4C47-B5F3-6333C3B0FB28}&View={8E6124E0-23F2-4BA2-86E7-96E7F36BAEC8}&RowLimit=0&RootFolder=%2fLists%2fSharepoint%20Sites
Selection={14C4ED2B-3050-4C47-B5F3-6333C3B0FB28}-{8E6124E0-23F2-4BA2-86E7-96E7F36BAEC8}
EditWebPage=
Formatting=None
PreFormattedTextToColumns=True
ConsecutiveDelimitersAsOne=True
SingleBlockTextImport=False
DisableDateRecognition=False
DisableRedirections=False
SharePointApplication=http://SharepointSite/_vti_bin
SharePointListView={8E6124E0-23F2-4BA2-86E7-96E7F36BAEC8}
SharePointListName={14C4ED2B-3050-4C47-B5F3-6333C3B0FB28}
RootFolder=/Lists/My list
You can take the third line which is -
http://SharepointSite/_vti_bin/owssvr.dll?XMLDATA=1&List={14C4ED2B-3050-4C47-B5F3-6333C3B0FB28}&View={8E6124E0-23F2-4BA2-86E7-96E7F36BAEC8}&RowLimit=0&RootFolder=%2fLists%2fSharepoint%20Sites
And use that to retrieve the complete list. I added an new receive data connection, selected an xml document and added the above URL.
It is not formated particullary nice but it will return all the data that I was expecting.
I think that Argalatyr solution is much simpler at this point, but it depends on if i am able to get the default view changed.
there is yet one workaround of this without such hardcoding. If you open Query editor, then you have there available ribbon with menu items. Open "Home" -> "Select top rows" and enter there some realy high number (I have in my list 596 rows, so I entered there as limit of top rows 20000 and I got whole list).
Sorry, I don't have available English version of Excel, so I cannot add screenshots.
enter image description here
I have something funky going on with MOSS & was wondering if anyone out there has seen anything like it:
I have a document library in MOSS that has several custom columns added to it. I have a column of type choice. For one document in the library (a word document), the selected value does not get displayed for the one column - all of the other columns are fine & the other 60 documents in the folder display the selected values correctly. When I edit the properties of the document, the value of the column is defaulted to blank, I can change it to another value & save it. However the new value doesn't get displayed in the list view, nor does it show up if I edit the properties again.
If, I open the document in word & view the Document Information Panel it displayes the value that I had selected & saved for the column. However, the column is being displayed as a text box & not a drop down. The value still does not get displayed in the list view or properties view after a save.
Has anyone seen behaviour like this before?
My first guess is a name collision between your custom column and the columns that ship with SharePoint out of the box. What is the column name that is causing the problem?
I have seen situations like this when there are documents in a library, and then columns are added. The existing information does not get updated properly.
If you reupload the document as a second content, does this happends again ?
If yes, you may check advanced properties of the document before uploadind it. There may be some data in it that SharePoint try to use when importing the file. It may explain that you don't have the issue when you copy/paste only the content.
Along a similar line, it could be that the problem doc has a Word metadata field named subject, and MOSS is doing its property promotion thing to mess up your field. If so, clearing the Word metadata might fix it.