I have a code to generate custom form on 2010, that will generate form control based on the field type. I used the same code in 2013 I am getting the 2010 People Picker field including the resolve and search options. There is not auto complete options also. Is there ay specific property I need to set to convert the field to 2013 type field.
Note: OOB form its working as expected 2013 PP field shows.
Use SharePoint:ClientPeoplePicker instead SharePoint:FormField
Complete solution :
Solution
Related
A Microsoft Word 2013 document at work has the Document Information Panel (DIP) displayed by default, with what is listed as "Document Properties - Server".
I'm trying to make a VB Macro that will involve editing these custom properties. However they don't seem to exist in ActiveDocument.CustomDocumentProperties, or ActiveDocument.BuiltInDocumentProperties. I know this because I ran through the list, displaying them one by one, as well as searching them by name.
The first property on the DIP called 'Title' showed up (in the latter list), but none of the other properties. It's worth noting that some are dropdowns, and one is a date with a calendar feature. I should also mention that I get a Run-time error near the end of the list of BuiltInDocumentProperties.
Is there another list where I can access these server properties, or some other issue that I'm overlooking? Any help would be appreciated.
I was able to find them. They are listed in ActiveDocument.ContentTypeProperties
I'm having trouble with Microsoft Access. I get the error "Run-time error '2683', There is no object in this control".
When debugging the database, it seems the line
Me.qStartDate.Value = Me.DTPickerStart.Value
is the problem. I've researched this error and it seems that there's a problem because DatePicker is deprecated and does not work on Access 2010. I'm wondering how I can rewrite this to make the function work.
Sorry, I'm a web programmer and I'm not very familiar with Visual Basic.
have a look at:
http://msdn.microsoft.com/en-us/library/office/gg251104(v=office.14).aspx
It mentions your options:
Use the built-in DatePicker feature for any TextBox control that is bound to a Date field.
Use the Windows DatePicker control, part of the Windows Common Controls.
Use a subform that looks and functions like a calendar.
Use a third-party date/calendar control.
In a VBA project, you can create a UserForm and add controls to it using the toolbox window. By default, the toolbox window contains the simple form controls such as Label, TextBox, ListBox, etc.
You can add additional controls if they're installed on your machine: right-clicking "additional controls" on the toolbox shows a whole screed of controls. However, this does not give any indication of where they came from.
I'm interested to know what controls are guaranteed to be available on a machine that has Office 2007 installed. Is it just the standard ones, or are some of the "additional controls" also guaranteed to be available (either because they come with Office 2007, or because they exist on all the versions of Windows that Office 2007 will run on)?
For example, I'm surprised that there's no treeview control even in Office 2007. In my "additional controls" list I see the "Microsoft TreeView Control v6", but I don't know whether I can rely on that being present for all my Office 2007 users.
The controls you see are part of FM20.DLL; which is part of the Office Install.
You can see that they are all part of the same DLL by looking in the "Location" portion of the "Additional Controls" box.
AFAIK, those are the only controls guaranteed available with most Office installations.
So that being said, let's see what can be done specifically for each control you ask about in your comments:
"grid" capable list
hierarchical tree view
calendar control
The Grid
It's going to come down to your requirements, but you may be able to get away with using a listbox. The listbox in VBA has a few of properties that make will make it Grid-like.
For example, let's say a worksheet in Excel looks like this:
ID001 Value 1 Description 1
ID002 Value 2 Description 2
ID003 Value 3 Description 3
The listbox supports multiple columns, so you can make these values show up by setting the listbox property ColumnCount to 3 and writing the following code:
Me.ListBox1.ColumnWidths = "50;100;200"
Me.ListBox1.RowSource = Sheet1.Range("A1:C3").Address
You will get something like this:
Want to hide a column? No problem, change the width of the ColumnWidths property to zero for the column to hide:
Me.ListBox1.ColumnWidths = "50;0;200" 'Hide column 2
What good is a grid if you can't select things from it, right?
On the listbox, change the ListStyle property to frmListStyleOption and then change MultiSelect to frmMultiSelect.
That will give you a listbox that looks more like a grid:
Calendar
08/17/2012 UPDATE:
Read this post. One of the guys who answered created his own calendar control.
A calendar control exists for Office (mscal.ocx):
However, the right conditions must be met:
Access must be installed on the clients machine
The Office version cannot be Office 2010 as it was removed with this version (See Features removed from Microsoft Access)
You can still get the calendar control to work with 2010 and/or non-Access Office installations, but it takes additional steps on the client's machine.
Download mscal.ocx
Extract it to windows/system32 directory
Register it
TreeView
If it's acceptable for you clients to install some EXEs, you could have them install Microsoft Visual Basic 6.0 Common Controls. That will give you the TreeView control.
I would be willing to bet that most machines (particularly older ones on Windows XP) already have these OCXs installed; thus the installation may not be necessary.
The biggest problem is that you're deploying OCXs on client machines and that gets frustrating from a support standpoint.
I created two lists in a SharePoint site: tbdl1 and tbdl2.
tbdl1 contains two datetime fields. One of these fields has default value set to now().
tbdl2 contains no additional fields other than title.
From list settings for each list, I customise and publish their InfoPath form (edit) to SharePoint.
Next, I add an InfoPath form web part to a SharePoint site and configure it to display tbdl1.
Until now, I can change the date time field fine.
The problem:
I add another InfoPath form web part to the same page and configure it to display tbdl2.
I try to change the date time field in tbdl1. The date field always resets to today's date. See illustration below.
Is this a SharePoint 2010 issue, InfoPath issue, or am I doning something wrong? You help is much appreciated.
I have created associations between entities in my .Net assembly BCS model. When I load the model into SharePoint and create external lists, I automatically get an External Item Picker control; enabling me to select an item from a list.
This is great because I don't have to program this pick list one way or another...
The problem is whenever I modify the form in InfoPath, the External Item Picker seems to break. When I select an item using the External Item Picker (in the InfoPath form) I get an error message "There has been an error while processing the form". This message is displayed as soon as I select an item and try to leave the field; WITHOUT submitting the form.
Can anyone tell me why the External Item Picker breaks whenever I modify and publish the list form from InfoPath 2010?
It's driving me nuts!
Thanks!
I've ran into the same issue, and found the following answer:
It's a bug from the August cumulative update.
Source
I am in the process of installing the February CU to see if it has the solution.