Web components have been a topic of conversation for some time, but I had never had a reason to really take time to explore building an application using them. There are many different reasons, with the biggest one being that many of the projects I have been working on utilize some of the big component libraries like Kendo or DevExpress. Continue reading “First Adventure into Web Components”
Since I am unable to post comments directly to this page because Disqus is refusing to send a verification email, I am posting the question here and hope someone can provide answers.
I understand building relationships, but I need to be able to do more than use a relationship in a lookup. I need to be able to display related records from an entity based on a currently selected entity in a parent table.
For example, say I am building a work order tracking system for techs and customers. I have a work order entity and a work order history entity I would like to use. The work order tracks the original request from the customer while the history tracks the individual touch points a tech has made with the customer. I have a screen that displays the details of the work order. I want to be able to display the full history of the work order (and add more records) by going from the currently selected entity. This scenario is almost entirely missing, and in my opinion a much more common use of relationships in entities.
Are there plans to support related data in a much more comprehensive manner? If not, this could be a very limiting factor with using both the common data model and PowerApps since a lot of data structures make use of relationships to expose related data.
I recently presented at the Dallas SharePoint TechFest on the topic of building HTML5 Apps for SharePoint 2013 using LightSwitch. This post is the first in a series of posts that further explains how the reference application reviewed during the session was built. The reference application is a mobile facing application used by remote service technicians to track and update logged work orders in a SharePoint issues list.
Recently, I had worked to help a client create an intranet portal and suddenly the portal started taking between 8 and 10 seconds to display the home page. All other pages in the solution were snappy and displayed very quickly. Returning to the development environment, the problem could not be reproduced and all pages continued to be displayed quickly. At first, it appeared the farm’s SQL server might be the issue so the developer dashboard was turned on to see where the bottleneck was occurring. After turning on the developer dashboard, it became very clear where the problem existed — a Content Query Web Part was taking on average about 8 seconds to render content.
Continue reading “Set Limits on XSLT Recursive Functions”
In a recent project, a co-worker described a scenario where users navigate to a site and review a handful of up to 30 or 40 reports/documents stored in the site. Each user visits the site on a periodic basis to review these various reports. My co-worker proposed allowing users to place links to the reports they need to review each period in a links library and then filter the default view to show links created by the current user. The client wanted to make it as easy as possible to add the report by including it as an option on the edit control block. In most cases, this would call for a farm solution that deploys a new ECB custom action. However, farm solutions are off limits — and this is a SharePoint 2007 environment so SPD custom actions are not available either.