Skip to main content

Linq to DataTables - The Easy Way

The Problem:

  • Couldn't easily read an excel file and query it programmatically.
  • Using JSON.Net took a little longer than I thought it would.
  • Wanted to brush up on my Linq skills.
  • This was a rush job


The Solution:

  • Utilized "Excel Data Reader", which allowed me to read Excel data and converted it to a DataSet
  • Used Linq to query the data easily, and produced manageable code (for me anyway)
  • Used JSON>NET to serialize my code and write to the DOM

Code Samples:

            DataRow dr = ds.Tables[0].Rows.Cast<DataRow>()
                .Where(row => row["Column1"] == DBNull.Value)

                .FirstOrDefault();

In this example, I'm wrote a simple Linq query which returned all rows in the DataTable what has any data in the first column. Not the most sophisticated, but you get the point.

What I've Learned:

Originally, I thought casting the DataTable as Enumerable was enough to bring back the desired result.  I had a lot of trouble creating a valid where clause, which caused a lot of casting and type comparison errors.  Rows.Cast<DataRow> resolved most of the issues. Essentially, casting the collection items to a DataRow type made it easy to grab the values I need quickly.

More Reading:

https://exceldatareader.codeplex.com/
http://stackoverflow.com/questions/12195952/making-a-datarow-select-query


Comments

Popular posts from this blog

Resolved Sitecore "If you publish now, the selected version will not be visible on the web site" warning

The Problem:   Unable to publish any Sitecore item within a particular site, even out of the workflow. Rather, a warning reads " If you publish now, the selected version will not be visible on the web site " What I've Discovered: I couldn't publish any item in the site, not just one or two I viewed all parent items of the items in question The main home page displayed a different warning " This item will never be published because it's publishable option is disabled " Another sitecore developer reminded me of the standard fields option View --> check standard fields to show all standard page fields Found out that somebody checked Never Publish within the publishing section The Fix: After I unchecked the checkbox and saved the change, I was able to publish again.  :) Conclusion: Looks like another Sitecore user thought the children items would not be affected by this change.  Lesson  learned.

[Resolved] Sitecore ParseException: End of string expected at position...

Problem:  I have a line of code that uses Sitecore Fast Query to pull all items + children starting with a site item, like so: Item [] allItems = db.SelectItems( "fast:" + sitecorePath + "//*" ); Unfortunately, I would get a Sitecore parsing error at runtime: ParseException: End of string expected at position... Turns out Sitecore doesn't like hyphens ('-') in any sitecore path when using fast query, which I have a few distributor sites in a folder which contained hyphens. Solution: I create a simple method that resolves a sitecore path to be Sitecore fast query friendly:             string sitecorePath = "" ;             if (siteItem.Paths.FullPath.Contains( "-" ))             {                 String [...

Create a File Upload Service using Node.js / Express / Multer

Problem:    I needed to create a form that essentially uploads a file to a server, then posts the rest of the form data to a second server with the new file name. In other words, post the image to an “Image” server, then posts the form data (with the file URL) to a “Form Data” server. Solution:  Create an Express server that uses the “Multer” library to accomplish this. The Code: Create the express server and have it listen on a specific port var express = require( 'express' ); var app = express (); app . listen ( 3313 , function (){     console . log ( 'listening on port 3313' ); }); Install Multer.  Read here: https://www.npmjs.com/package/multer Include Multer to your express app.  We’ll be tweaking the storage properties so you can name the file whatever you like. At the end, you should have an “upload” object you’ll be using in the next step. be sure to change the file destination of your choice. var expre...