Is there a way to generate classes only tables those got changed (column added, column modified, column deleted etc.)?
Not really, but there's usually no reason to worry about that. If you have custom code that you don't want overwritten you can put it in a partial class. Was that the issue?
Related
I got a view where the fist column is categorized by one field and the second column is categorized with more values separated with "\".
I now try to get a document by key, it does not work until I remove the category option from the second column. I tried getEntryByKey, getAllEntriesByKey, getDocumentByKey, getAllDocumentsByKey in SSJS and in Java. I tried it just for fun with an LotusScript Agent and it works.
Another way that works is createViewNavFromCategory. But I also have some views where the first column is only sorted and of cause than this solution does not work for me.
Is that an known issue? Is there a way to work around this problem?
UPDATE:
I just want to use the first column for getDocumentByKey
I'd suggest trying in a Java agent. If that doesn't work, I'd raise a PMR. There are some differences between Java and LotusScript, so it's possible that it doesn't work. I found a similar inconsistency with number values (which should be fixed in 9.0.2, I believe) http://www.intec.co.uk/apparent-java-getalldocumentsbykey-getallentriesbykey-bug/
It may be that "\" gets escaped in Java, so you may need extra characters, same as you would in Formula Language
I am using tablix and group my entries by one of the properties. I have some trouble with SSRS when exporting my report to Excel. The very first row of each group is added to the end of its group.
This only(!) happens when exporting the report to Excel, exporting to any other format will leave my table the way it should be:
Thank you for your help!
I see that this is an old question but I have the same problem and I've been able to solve it just changing the Visibility property of the different tablix components.
In my case I have this.
Row Visibility: "Hide" and also set "Can be toogle by" with the parent group.
Group Visibility: "Show".
Each textbox of the detail row Visibility: "Show".
It looks like it is not removing dupes for you in the grouping that repeat. Are you doing a regular grouping with property or a function? There are two solutions for this:
Ensure your dataset is having distinct values (even if you think you are certain). If this is standard 'select' statement to a SQL Server just add Select 'Distinct' and your values.
I would try maybe making the properties in the table that are in the lowest level, shown as '[Details]' generally in the design section under 'Row Groups'. Change the properties to be something like:
[Max(propertyb)] and [Max(propertyc)]
This is not needed generally as the grouping should be taking care of this. But in cases where it is not it is an extra level of logic may fix the issue. You also need to be aware depending on your grouping logic that if it is not grouping properly you may get the same result for that many rows. This would not be as advised as it is more of a hack to get what you want, not an elegant solution.
I want to create a custom field with multiple values like it may store array variables.
also this field is not a lookup field.
what can be the field type that I should inherit from to achieve this ?
thanks
SPFieldMultiColumn may well be the class you're looking for. Here is the relevant MSDN article:
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spfieldmulticolumn.aspx
Good luck with it though, custom fields can be a pain in the ears at the best of times.
I created a custom Revision column in one of my document libraries and required data to be put into it. The document library had some documents in it and I tried uploading a file. I put the data in Name and Revision, but it gave me an error that I was missing information. So I checked the columns in site settings and found 2 Revision columns that each required information and only one would be displayed when editing/entering new information. I deleted the column from that library, and I had to delete it from many other libraries as well.
It seems to only happen with libraries that have content. None of my empty libraries have this problem, only the ones with documents.
Is this a problem with SharePoint, and if so, what can I do to avoid this problem?
If there is no way to avoid it, is there a way to delete all the extra cloned columns?
Thanks.
I had moved the files from one folder to another and it created a second Revision column since the two did not match. When you move items from one library to another, you should try moving the items before adding the columns because the columns will be auto generated. I had this happen to me again when I move Contacts from one list to another.
I Want to have only unique values in a SharePoin List. To achieve this I can use 'ItemAdding' event handler as mentioned in the below link.
http://weblogs.asp.net/vikram/archive/2008/12/24/sharepoint-using-event-handler-to-make-a-column-unique.aspx
Now I have a Doubt: Suppose that two user tries to add list Item in the list with the same column value(which requires unique value) at the same Time. will ItemAdding event would be fired at the same time for both call? If so then there is a possibility that two items having same value in the column. Please confirm.
I think, this method allows you only to have semi-unique values in the column. That is, if everything is normal, it will be unique. However, you cannot compare the properties of two items being added simultaneously (and yes, it may happen, since IIS web server is multi-threaded). Hence you might have duplicate values as a result.
A workaround - implement a "ItemAdded" event handler, too and delete a newly added item, if it has that property the same as some other existing item. This will, of course, happen very rarely.
If you have enough concurrent users that this is likely to be a problem, SharePoint probably isn't the right tool for the job. If the value is created by the user, it is extremely unlikely that two users will be adding the same value at the same time. If it is automatically generated, you probably should be using something based on ID, which is known to be unique.
If you are worried about the possibility of duplicates anyway, just make sure that the field can be edited if you do end up with duplicates causing problems.