I have a problem deleting a custom field from a vendor in NetSuite. When I try to delete it I get the following error message.
This custom field cannot be deleted because it is referred to by other custom fields
I've looked at many of my other custom fields and columns but I can't find any that are referencing this one. Is there a way to find all fields that refer to a particular custom field?
This is because you might be using this custom field value some where else. I'm not sure if there is any inbuilt functionality to identify the other fields which are being referred by your custom field. I had a similar issue but I solved it using mass update. I set that field value for all the vendor as blank then I was able to delete the custom field.
In case it is a custom list field then follow the steps bellow :
First delete the list from Setup > Customization > Transaction Item Options, then from the Custom Item Fields and then finally from the Custom Lists
To narrow down the list of fields to check, go to Customization->Lists, Records & Fields->Entity Fields. Sort that list by the Vendor column. That is the list that needs to be checked. Open each of these fields, and check that the 'Field' under the 'Validation and Defaulting' tab is not your custom field that you want to delete. Then check the values on the 'Sourcing and Filtering' tab as well.
Good luck, and hopefully there is not too many vendor fields to check this way!
I need the end user to select which field he wants updated. Is there an option to have a lookup input parameter that let's the user select a field of the current entity?
I need it to perform operations on the value of the selected field.
As far as I know there isn't a custom type to handle a list of fields (or a list of strings) as InputParameter for a Custom Workflow Activity.
The (ugly) alternative is to use a string parameter where the user enters the field name.
If the list of fields isn't very big, you could add an optionset to the form with those field names and then your workflow could have If conditions based on that optionset.
I strongly suggest you to use a dialog to complete this. You can set the stage, the parameter and based on the situation the values to insert. Also you can execute workflows from the dialog itself.
If the record already exists, consider registering a plug-in on the update message. When in update the request InputParameter["Target"] contains only dirty fields changed by the user.
Instead of creating a list of fields you can create another (role) form to limit the fields the user can edit on the form.
i have create one custom field in calender i want to search event whic meets custom field criteria how it can be possible because there is no method which in service class
Custom attributes are stored in the Expando* tables in Liferay and depending on how you define the custom fields it can also provide indexing and searching for you. It's a bit hard to say more without knowing more, I guess.
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.
In a SharePoint list I want an auto number column that as I add to the list gets incremented. How best can I go about this?
Sharepoint Lists automatically have an column with "ID" which auto increments. You simply need to select this column from the "modify view" screen to view it.
You can't add a new unique auto-generated ID to a SharePoint list, but there already is one there! If you edit the "All Items" view you will see a list of columns that do not have the display option checked.
There are quite a few of these columns that exist but that are never displayed, like "Created By" and "Created". These fields are used within SharePoint, but they are not displayed by default so as not to clutter up the display. You can't edit these fields, but you can display them to the user. if you check the "Display" box beside the ID field you will get a unique and auto-generated ID field displayed in your list.
Check out: Unique ID in SharePoint list
If you want to control the formatting of the unique identifier you can create your own <FieldType> in SharePoint. MSDN also has a visual How-To. This basically means that you're creating a custom column.
WSS defines the Counter field type (which is what the ID column above is using). I've never had the need to re-use this or extend it, but it should be possible.
A solution might exist without creating a custom <FieldType>. For example: if you wanted unique IDs like CUST1, CUST2, ... it might be possible to create a Calculated column and use the value of the ID column in you formula (="CUST" & [ID]). I haven't tried this, but this should work :)
I had this issue with a custom list and while it's not possible to use the auto-generated ID column to create a calculated column, it is possible to use a workflow to do the heavy lifting.
I created a new workflow variable of type Number and set it to be the value of the ID column in the current item. Then it's simply a matter of calculating the custom column value and setting it - in my case I just needed the numbering to begin at 100,000.
it's in there by default. It's the id field.
If you want something beyond the ID column that's there in all lists, you're probably going to have to resort to an Event Receiver on the list that "calculates" what the value of your unique identified should be or using a custom field type that has the required logic embedded in this. Unfortunately, both of these options will require writing and deploying custom code to the server and deploying assemblies to the GAC, which can be frowned upon in environments where you don't have complete control over the servers.
If you don't need the unique identifier to show up immediately, you could probably generate it via a workflow (either with SharePoint Designer or a custom WF workflow built in Visual Studio).
Unfortunately, calculated columns, which seem like an obvious solution, won't work for this purpose because the ID is not yet assigned when the calculation is attempted. If you go in after the fact and edit the item, the calculation may achieve what you want, but on initial creation of a new item it will not be calculated correctly.
As stated, all objects in sharepoint contain some sort of unique identifier (often an integer based counter for list items, and GUIDs for lists).
That said, there is also a feature available at http://www.codeplex.com/features called "Unique Column Policy", designed to add an other column with a unique value. A complete writeup is available at http://scothillier.spaces.live.com/blog/cns!8F5DEA8AEA9E6FBB!293.entry
So I am not sure I can really think of why you would actually need a "site collection unique" id, so maybe you can comment and let us know what is actually trying to be accomplished here...
Either way, all items have a UniqueID property that is a GUID if you really need it: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.splistitem.uniqueid.aspx
Peetha has the best idea, I've done the same with a custom list in our SP site. Using a workflow to auto increment is the best way, and it is not that difficult. Check this website out: http://splittingshares.wordpress.com/2008/04/11/auto-increment-a-number-in-a-new-list-item/
I give much appreciation to the person who posted that solution, it is very cool!!