I have Lightswitch 2013 and need to have nested autocomplete boxes. All the examples on the Internet are for older versions of Lightswitch and there are just a few differences in their examples from my version. Example: When adding Data Item for Local Property, Type "someTable" (Entity) doesn't come up as a choice. Also, if I click on one of my tables, then when I drag this Local Property to the screen is doesn't create an autocomplete box. Seems simple, but frustrating when I've tried many different ways. Please provide specific example using Lightswitch 2013. Thanks in advance. Steve
The steps are:
(1) Create a table called Customers(Id, Name) and a table called Orders(Id, CustomerId, Description) Create a foreign key relationship between Customers.Id and Orders.CustomerId.
(2) Update your LightSwitch 2013 Data Source
(3) Create an Add/Edit screen using the Orders table.
(4) By Default, all the fields (Id, Customer, Description) should be included. The Customer field should default to 'Details Picker' (The Choices will be 'Auto' and will lookup Customers in the Customers table)
Note: The Details Picker will AutoComplete after you type a minimum of three characters.
Thanks for the answer. I figured it out myself. I played around with displaying fields on my screens to see what was actually happening until I finally found out that I can add a specific data binding? to my properties and didn't have to use the drop down choices. I've got it working now.
This seems like a basic requirement for using Lightswitch. I wish someone would be able to post a detailed step by step solution to properly using nested autocomplete boxes. I'm not sure I would remember how to do nexted autocomplete boxes if I had to do this again in a year.
When an expert, like a Beth Massi, provides a detailed example for a specific version of Visual Studio or Lightswitch, it would be nice if that expert, or his/her replacement, would provide a new detailed example whenever Visual Studio or Lightswitch has a new version. Thanks for all the help I have received by searching the Internet.
Related
I'm using the Visual Studio Team Foundation Server 2013 web interface and have created and saved many queries with custom columns, sort orders etc.
However, when creating a new query or doing a "search" (i.e. the "Search work items" control in top right of Queries page) the default columns are always: ID, Work Item Type, Title, State, Assigned To and Tags.
How do I change the default columns so that all new queries will default to my preferred columns?
Thanks
From an MSDN forum post:
And for these work items which are shipped with TFS Server, the information is stored in the team project template. For example, if you are working with a Agile team project, go to MSF for Agile Software Development v5.0\WorkItem Tracking\Queries, select the query you would like to custom the displayed columns and make changes.
For Visual Studio the change is different. This setting is changed via the registry at this location:
Computer\HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\<versionNumber>\WorkItemTracking\QuerySettings\ColumnSetting
I haven't found a consistent Name for the key that affects this default between versions so the item you need to change depends on your version. A little trial and error should narrow down which key to change.
MSDN forum source
You have to add your desired columns for every single work item query via editing columns in the Column Options page. I can't figure out you one way to save default column options to use for new created work item queries.
For example, to add other columns in the Search query, you need to click Column Options function in the Editor page to choose columns you want.
We've just set up Dynamics CRM 2013. We're using the Outlook 2010 plug-in. A new entity has been created called "Projects," in which the users give the project a name (which is fairly long: Typically something like "2014 Project Name Client Name") and we assign activities and track emails to that project. The problem is that the project name in the blue bar doesn't truncate; instead it spills over the drop-down arrow (which lets you see related activities, contacts, etc) and is un-clickable. Logging in through the web interface, it truncates properly. Is there a way we can force it to truncate after a certain amount of letters, or use the ProjectID field for that label instead of the name? I'm fairly new to Dynamics so a simple solution would be much, much preferred.
A screenshot with an arrow pointing to the over-running field:
We had the same problem when using IE8. In IE9, the long name is truncated properly so the related button/link/whatever it is works as expected. MS unlikely to fix this issue in IE8 just fyi. If it's a custom entity, the primary key field will be the name and that field is used in the UI when it wants to show a record. So you have two options. Change the browser version or only use short names.
I am new to Dynamics CRM so please excuse me for the newbie question xD
I managed to create an option set field with 2 possibilities:
Scheme 1
Scheme 2
Does anyone have an idea how when a particular possibility is picked, a list of custom based fields will appear in the form? Thanks in advance
If i understand your problem correctly you want certain fields to appear/disappear according to the choice selected in the option set.
The way I see this working is by implementing a Javascript on the onChange event of the option set. you can do this from the 'Form Properties' when changing the layout of the form.
Below is a link showing some examples of possible useful commands that might help you:
http://www.powerobjects.com/blog/2011/01/14/crm-2011-useful-javascript-tidbits/
You can put your custom fields in a custom tab and then hide/disable it according to the value in the option set.
If you have any further problems feel free to ask :)
I hope this helps :)
Gdluck
If you are comfortable working in Visual Studio, I highly recommend installing the Developer Toolkit (You can find the .msi \tools\developertoolkit - download it from here). It will allow you to develop JScript with some syntax highlighting and intellisense and makes source control and deployment a snap.
I am working on the Visual Studio using MFC. I want to make a table having rows and columns. Rows with four entries and columns entries have no limits. Which toolbox I should use in order to proceed in this task. I tried listbox, combo box, mfc vslist but these are not fulfilling my requirements. Kindly guide me which tool box I should use for this purpose. I get some kind of info from that link http://www.functionx.com/visualc/controls/listbox.htm but this is not required.
According to your description, you can use the standard List Control (CListCtrl) in report mode or, if more advanced features are needed, a full-blown grid control. In codeproject you can find these two, which are quite widely used:
MFC Grid control
The Ultimate Grid
I don't know if they work well with VS 2010, but the first one, according to the link provided, it does. The Ultimate Grid says it works up to VS2005, but I'm using it with VS2008. I don't remember if I had to change anything in order to make it work, though.
Anyway, I would first give the standard CListCtrl a try, and if you find you need more, try any of the others.
When entering a work item in TFS2010, it's often nice to refer to other tickets in the text free fields (either description or Acceptance Criteria field).
Most other ticket tracking software I have used automatically creates links/hyperlinks to other tickets if you put appropriate text into these fields (e.g, Trac, BugTracker.NET, etc).
I understand the link tab, and that you can create relationships there, but it would be lovely to have this feature available and clickable in the other text field.
Does TFS2010 (+ Visual Studio 2010) support something like this? I cannot find for the life of me, a solution.
If you use a rich text edit field (the advanced text field available for work item definitions, with coloring buttons and so on), you can include hyperlinks, also to other workitems etc. This is however a manual exercise to make the hyperlink point to the correct item, there is no automatic recognition of #-tags or whatever to refer to other workitems.
Hi you could use a plugin called TFS Extensions Kit. TEK workitem. This is a Visual Studio extension that allows, besides other features, to open, in Visual Studio, workitems and queries from a Hyperlink.
So you could use the hyperlinks in any field.
Look at the Visual Studio Gallery:TFS Extensions Kit. TEK workitem
You can download a demo from here
Regrads
It's an old question, but if you get here looking for the answer for VSTS the answer is hashtag followed by itemId. Similar to #UserName to reference another user.
Eg. In comments box typing This is a dupe of #2428 will translate into This is a dupe of User Story 2428: Story name where User Story 2428: Story name is a link to the item.