Category Archives: SharePoint garapena

HTTP 406 Akatsa When Angeluen $ http.get erabiltzea SharePoint REST End Points Against

Eguneratu: Marc AD ndersson pointed out this great piece of info: http://blogs.office.com/2014/08/13/json-light-support-rest-sharepoint-api-released/. That explains a lot :).

That may be the worst title of a blog post ever! Anyhoo.

I typically do all of my prototyping against an O365 instance. I have my personal instance so that I don’t have to be worried about affecting anyone else. As an aside – remember when we call carried around virtual machines on our laptops with MOSS – SQL Server, IIS, deciding Hyper-V vs. VMWare? Anyhoo…

I had developed an app using Angular in this environment that does, beste gauza batzuen artean, honetan:

$http.get(serverUrl)
.success(funtzioa(data, egoera, headers, config) {

var getLinksResponse = data;

getLinksResponse.value.forEach(funtzioa(theResult) {

// and so on and so froth

This was working just fine in two different SharePoint online environments. Hala eta guztiz ere, when my colleague ported it to a Cloudshare instance, he was getting an HTTP 406 error (which was the first time I ever got that one, so … yay, I guess). We did a bit of research and noticed that the “Accept” header was off. SharePoint online was perfectly happy with:

Accept: application/json

But the cloudshare instance (which is SP on prem, hosted in a virtual server) wanted the classic “odata=verbose” added in as well:

Accept: application/json;odata=verbose

To fix that, we added the header as such:

var config = {headers: {
‘Accept’: ‘application/json;odata=verbose’
}
};

$http.get(serverUrl,config)
.success(funtzioa(data, egoera, headers, config) {

var getLinksResponse = data;

getLinksResponse.value.forEach(funtzioa(theResult) {

// and so on and so froth

That got rid of the 406, but it also changed the format of the response. It was more … verbose. (haha!) More changes were required and here’s the final result:

var config = {headers: {
‘Accept’: ‘application/json;odata=verbose’
}
};

$http.get(serverUrl,config)
.success(funtzioa(data, egoera, headers, config) {

var getLinksResponse = data;

getLinksResponse.d.results.forEach(funtzioa(theResult) {

// and so on and so froth

This only turned into a 30 minute problem for us, so we lucked out. Hopefully someone finds this useful.

</amaiera>

Laborantza Sentsibilizazioa / JavaScript Frameworks onesteko

Nire lankide, Javed Ansari (http://www.bigapplesharepoint.com/team?showExpertName=Javed%20Ansari&rsource=pgblog), wrote a short summary blog post on frameworks he likes or at least has been using with with SharePoint: http://www.bigapplesharepoint.com/pages/View-An-Insight.aspx?BlogID=53&rsource=PGBlog).

jQuery seems to have been the victor on the field, so to speak, for years now, but the others are more new and stills sort of battling it, like Angular. (SPServices, jakina, has been a life saver for years and will continue to be so I think).

What are people using? Are they focused more on Microsoft’s tooling (CSOM / JSOM) or moving more toward Angular, Knockout, Ember, etc?

I have a growing bias toward these non-Microsoft frameworks. I think the MSFT stuff is harder and harder to work with, requiring almost as much of learning curve as old-style server-side dev.

Post a comment here or over at Big Apple SharePoint if you want to discuss (Big Apple will have more likelihood of a good discussion).

</amaiera>

SharePoint Timer Jobs spinning from Site Bilduma konfigurazioa

Nire lankide, Ashish Patel, wrote a blog post describing a flexible timer job architecture that affords some nice flexibility to support long-running tasks and/or reports.  In his words:

1. Analyzing Checked out files and sending reminders to the individuals if the number of days (since the file was checked out) exceed certain threshold limits

2. Removing links from other content when a particular content is removed or archived from the system

3. User wants to see all the alerts that he subscribed in all webs in the site collection

4. Sending a reminders to authors to review the content when a review time was specified in the content and that date is approaching

Beno, the list goes on…

– See more at: http://www.bigapplesharepoint.com/pages/View-An-Insight.aspx?BlogID=40#sthash.7cKuiwly.dpuf

There are times in my past when having something like this would have been very helpful.

</amaiera>

Nola: Konfiguratzeko Unitateko testa eta Test Estaldura QUnit.js eta Blanket.js batera Office batentzat 365 SharePoint App

Intro

I’ve been exploring unit testing and test coverage for JavaScript as I work on a new SharePoint app for SharePoint online in the Office 365 suite.  The obvious research paths led me to Qunit.js and right after that, to Blanket.js.

QUnit let me set up unit tests and group them into modules.  A module is just a simple way to organize related tests. (I’m not sure I’m using it as intended, but it’s working for me so far with the small set of tests I have thus far defined).

Blanket.js integrates with Qunit and it will show me the actual lines of JavaScript that were – and more importantly – were not actually executed in the course of running the tests.  This is “coverage” – lines that executed are covered by the test while others are not.

Between setting up good test cases and viewing coverage, we can reduce the risk that our code has hidden defects.  Good times.

Qunit

Assuming you have your Visual Studio project set up, start by downloading the JavaScript package from http://qunitjs.com.  Add the JavaScript and corresponding CSS to your solution.  Mine looks like this:

image

Figure 1

Ikusten duzun bezala, I was using 1.13.0 at the time I wrote this blog post. Don’t forget to download and add the CSS file.

That out of the way, next step is to create some kind of test harness and reference the Qunit bits.  I’m testing a bunch of functions in a script file called “QuizUtil.js” so I created an HTML page called “QuizUtil_test.html” as shown:

image Figure 2

Here’s the code:

<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
    <izenburua>QuizUtil test with Qunit</izenburua>
    <lotura rel="stylesheet" href="../CSS/qunit-1.13.0.css" />
    <script mota="text/javascript" src="QuizUtil.js" data-cover></script>
    <script mota ="text/javascript" src ="qunit-1.13.0.js"></script>
    <script mota ="text/javascript" src ="blanket.min.js"></script>

    <script>
        module("getIDFromLookup");
        test("QuizUtil getIDFromLookupField", funtzioa () {
            izan zen goodValue = "1;#Paul Galvin";

            equal(getIDFromLookupField(goodValue) + 1, 2), "ID of [" + goodValue + "] + 1 should be 2";
            equal(getIDFromLookupField(undefined), undefined, "Undefined input argument should return undefined result.");
            equal(getIDFromLookupField(""), undefined, "Empty input argument should return an undefined value.");
            equal(getIDFromLookupField("gobbledigood3-thq;dkvn ada;skfja sdjfbvubvqrubqer0873407t534piutheqw;vn"), undefined,"Should always return a result convertible to an Integer");
            equal(getIDFromLookupField("2;#some other person"), "2", "Checking [2;#some other person].");
            equal(getIDFromLookupField("9834524;#long value"), "9834524", "Large value test.");
            notEqual(getIDFromLookupField("5;#anyone", 6), 6, "Testing a notEqual (5 is not equal to 6 for this sample: [5;#anyone]");

        });

        module("htmlEscape");
        test("QuizUtil htmlEscape()", funtzioa () {
            equal(htmlEscape("<"), "&lt;", "Escaping a less than operator ('<')");
            equal(htmlEscape("<div class=\"someclass\">Some text</div>"), "&lt;div class=&quot;someclass&quot;&gt;Some text&lt;/div&gt;", "More complex test string.");
        });

        module("getDateAsCaml");
        test("QuizUtil getDateAsCaml()", funtzioa () {
            equal(getDateAsCaml(berria Data("12/31/2013")), "2013-12-31T:00:00:00", "Testing hard coded date: [12/31/2013]");
            equal(getDateAsCaml(berria Data("01/05/2014")), "2014-01-05T:00:00:00", "Testing hard coded date: [01/05/2014]");
            equal(getDateAsCaml(berria Data("01/31/2014")), "2014-01-31T:00:00:00", "Testing hard coded date: [01/31/2014]");
            equal(getTodayAsCaml(), getDateAsCaml(berria Data()), "getTodayAsCaml() should equal getDateAsCaml(new Date())");
            equal(getDateAsCaml("nonsense value"), undefined, "Try to get the date of a nonsense value.");
            equal(getDateAsCaml(undefined), undefined, "Try to get the date of the [undefined] date.");
        });

        module("getParameterByName");
        test("QuizUtil getParameterByName (from the query string)", funtzioa () {
            equal(getParameterByName(undefined), undefined, "Try to get undefined parameter should return undefined.");
            equal(getParameterByName("does not exist"), undefined, "Try to get parameter value when we know the parameter does not exist.");

        });

        module("Cookies");
        test("QuizUtil various cookie functions.", funtzioa () {
            equal(setCookie("test", "1", -1), getCookieValue("test"), "Get a cookie I set should work.");
            equal(setCookie("anycookie", "1", -1), Egia, "Setting a valid cooking should return 'true'.");
            equal(setCookie("crazy cookie name !@#$%\"%\\^&*(()?/><.,", "1", -1), Egia, "Setting a bad cookie name should return 'false'.");
            equal(setCookie(undefined, "1", -1), undefined, "Passing undefined as the cookie name.");
            equal(getCookieValue("does not exist"), "", "Cookie does not exist test.");
        });

    </script>
</head>
<gorputza>
    <div id="qunit"></div>
    <div id="qunit-fixture"></div>

</gorputza>
</html>

There are several things happening here:

  1. Referencing my code (QuizUtil.js)
  2. Referencing Qunity.js
  3. Defining some modules (getIDFromLookup, Cookies, eta beste batzuk)
  4. Placing a <div> whose ID is “qunit”.

Gero, I just pull up this page and you get something like this:

image

Figure 3

If you look across the top, you have a few options, two of which are interesting:

  • Hide passed tests: Pretty obvious.  Can help your eye just see the problem areas and not a lot of clutter.
  • Module: (drop down): This will filter the tests down to just those groups of tests you want.

As for the tests themselves – a few comments:

  • It goes without saying that you need to write your code such that it’s testable in the first place.  Using the tool can help enforce that discipline. Esate baterako, I had a function called “getTodayAsCaml()".  This isn’t very testable since it takes no input argument and to test it for equality, we’d need to constantly update the test code to reflect the current date.  I refactored it by adding a data input parameter then passing the current date when I want today’s date in CAML format.
  • The Qunit framework documents its own tests and it seems pretty robust.  It can do simple things like testing for equality and also has support for ajax style calls (both “real” or mocked using your favorite mocker).
  • Going through the process also forces you to think through edge cases – what happens with “undefined” or null is passed into a function.  It makes it dead simple to test these scenarios out.  Good stuff.

Coverage with Blanket.js

Blanket.js complements Qunit by tracking the actual lines of code that execute during the course of running your tests.  It integrates right into Qunit so even though it’s a whole separate app, it plays nicely – it really looks like it’s one seamless app.

This is blanket.js in action:

image Figure 4

image

Figure 5

(You actually have to click on the “Enable coverage” checkbox at the top [see Figure 3] to enable this.)

The highlighted lines in Figure 5 have not been executed by any of my tests, so I need to devise a test that does cause them to execute if I want full coverage.

Get blanket.js working by following these steps:

  1. Download it from http://blanketjs.org/.
  2. Add it to your project
  3. Update your test harness page (QuizUtil_test.html in my case) as follows:
    1. Reference the code
    2. Decorate your <script> reference like this:
    <script mota="text/javascript" src="QuizUtil.js" data-cover></script>

Blanket.js picks up the “data-cover” attribute and does its magic.  It hooks into Qunit, updates the UI to add the “Enable coverage” option and voila!

Laburpena (TL; DR)

Use Qunit to write your test cases.

  • Download it
  • Add it to your project
  • Write a test harness page
  • Create your tests
    • Refactor some of your code to be testable
    • Be creative!  Think of crazy, impossible scenarios and test them anyway.

Use blanket.js to ensure coverage

  • Make sure Qunit is working
  • Download blanket.js and add it to your project
  • Add it to your test harness page:
    • Add a reference to blanket.js
    • Add a “data-cover” attribute to your <script> Etiketa
  • Run your Qunit tests.

I never did any of this before and had some rudimentary stuff working in a handful of hours. 

Happy testing!

</amaiera>

undefinedNire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Lists.asmx, GetList eta "balioa ezin izango da null”

Gaur egun aurkitu nuen GetList dela() metodoa lists.asmx web zerbitzua deitu behar da kontu handiz edo joera da misteriotsu bat bota "Balio ezin da hutsik egon" salbuespen (Eta hori da suposatuz errore are okerragoa generic mezua iragan dezakezu, “Exception of type ‘Microsoft.SharePoint.SoapServer.SoapServerException’ izan zen bota. ")  Zehazki, Ezin duzula ematen GetList metodoaren aurrizkia inolako aurkitu dut.  Ondorengo mozkina jQuery puntua erakusten:

image

Egiten baduzu, web zerbitzua "Balio ezin da hutsik egon" honen arabera erantzuten FIDDLER-emandako HTTP espedientea:

<?xml version="1.0" encoding="utf-8"?>
  <xaboi:Gutun-azal
     xmlns:xaboi ="
http://schemas.xmlsoap.org / xaboi / gutunazal /"    
     xmlns:xsi = "
http://www.w3.org/2001/XMLSchema-instance"
     xmlns:xsd ="
http://www.w3.org/2001/XMLSchema">

  <xaboi:Body>
    <xaboi:Errua>
      <faultcode>xaboi:Zerbitzari</faultcode>
      <faultstring>
        Exception of type ‘Microsoft.SharePoint.SoapServer.SoapServerException’ bota zen.
      </faultstring>
      <Xehetasun>
        <Errore katea xmlns ="
http://schemas.microsoft.com / SharePoint / xaboi /">
Balioa ezin da hutsik egon.
        </errorstring>
      </Xehetasun>
    </xaboi:Errua>
  </xaboi:Body>
</xaboi:Gutun-azal>

Jakina, seguruenik ez duzu zure kabuz "S0" aurrizkia duten, Tresna baina joera batzuk ere egin (Eclipse bezalako).

Hau da, are nahasgarria / beste metodo jasaten aurrizkiak delako frustrating.  Esate baterako, duen GetListCollection metodoa ez du axola ari bada aurretik, are like "xyzzy" aurrizkiak zentzugabekeria batekin:

image

Hau "balioa ezin da hutsik egon" badirudi nahiko ohikoa lists.asmx, beraz, espero dugu hau norbaiti laguntzeko izango da etorkizunean.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Etengabe nidificantes <div> Tags eta jQuery

Hau oddball gaia halako dirudi, Ez dakit, benetan merezi blogging buruz da, Baina hori ez da inoiz gelditu me aurretik, beraz, hemen goaz Smile

Kanpo lan egiten dut proiektu bat non zenbait datu naiz tira bilaketa bat aurrera, it PACKAGING sortu XML mezua sartu eta, ondoren, XML hori, azken finean HTML bihurtzen XSLT bidez.  Bertan, parte hartzen duten jQuery asko, horietako bat bit tabbing funtzionalitateren bat burutuko du.  Noiz egin klik fitxa bat duzu (benetan, bat <div>), jQuery deitzeko. ezkutatu() eta. show() divs hainbat (Hasierako orria karga eduki guztiak deskargatzen daude, kasu honetan, beraz, ez postbacks).

A ordu mordo ago, fitxa kommutazio logika History hasi zen, eta ez zen nire fitxak bat erakusteko.  Jarraituko dut, azken finean, bertan behera Izan ere, Internet Explorer (gutxienez) pentsatu duten <div> tags habiaratuta urrun, urrun sustatzailearen intended.The toolbar baino sakonagoa izango litzateke erakusteko:

-<div id = "Tab1Content">
  -<div>
    -<div>
      -<div id = "Tab2Content">
        -<div>
           ..............................
                   </div>  <-Azkenik itxi egin zuten modu guztiak behera hemen erakusten!

Beraz,, nuen bat bada $("# Tab1Content").ezkutatu(), Era berean nuke ezkutatu Tab2 eta inoiz izan nuen erakusteko Tab2 nuen ez bada ere erakusten Tab1.  Kopiatu eta itsatsi dut kodearen sortu estudioan sartu eta ikusmen div horrek estaldura guztia erakutsi zuen nicely, bezala ziren ustezko izango da egiten ari, hau atsegin bila:

-<div id = "Tab1Content">
  +<div>
  +<div>
-<div id = "Tab2Content">
  +<div>
  +<div>

Nire burua beat dut pixka bat hormaren kontra, eta nabaritu da benetako HTML kode zela hutsik asko sortzen <div> Euskal Herria, bezala:

<gorputza>

  <div id = "Tab1Content">

    <div id = "row1" />
    <div id = "ROW2" />

  </div>

  <div id = "Tab2Content">

    <div id = "row1" />
    <div id = "ROW2" />

  </div>

</gorputza>

(Goiko da waaaaaaaaaaaay oversimplified.  Hutsik div tags guztiz baliozko. Nire batzuk <div> etiketa eduki beteta, baina beste asko ez ziren.  Izan zen gauzatu nuen nire <xsl:-bakoitzak> zuzentarau ziren labur-inprimaki div tags igortzen denean xsl du:-bakoitzean ez zuen 'aurkitu daturik.  HTML iruzkin bat behartu dut irteera sartu, ikus daitekeen bezala:

image

 

Egin nuen, eta ondoren, div guztiak egin lerrokatuta nicely eta nire fitxa aldatzen hasi zen lanean.

Beti bezala, Hau pixka bat norbaitek laguntzen espero dut.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Causa ", hutsegitea honen sortzailea ez Arrazoia ez da zehaztu.”

Izan dut lan asko egiten ari SharePoint bilaketa azkenaldian eta, zehazki, KeywordQuery klasea, propietate eta metodo.

Nahi duzun emaitza ezarri emaitzak itzuli eta batez ere haratago ohiko susmoa baduzu (ikusi hemen), gehitu duzun SelectedProperties bilduman, bezala:

myKeywordQuery.SelectProperties.Add("xyzzy");

Eskerrik asko eta kapela punta-a Corey Roth eta hau oso lagungarria blog post (http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2008/02/19/how-to-use-the-moss-enterprise-search-keywordquery-class.aspx)

Nire kasuan, "Xyzzy" ez da benetan kudeatzen propietate bat.  Denean gehitu dut hala ere SelectedProperties, SharePoint bota inoiz nire gogoko exekuzio salbuespen bat:

"Errua honen sortzailea ez du zehaztu arrazoia."

Gustuko dut, batez ere hiriburuan "R" Arrazoia da.  Hau niri soinuak. NET baliokideak bezala "Ahoa ez dut, eta garrasi egin behar dut."

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Handy Erreferentzia: KeywordQuery Search lehenetsia emaitzak

Noiz exekutatu deitu behar duzu() KeywordQuery batean metodoa, ResultType.RelevantResults oinarritutako ResultTable bat sor dezakezu.  Kodea snippet honek erakusten du zer esan nahi:

ResultTableCollection resultsTableCollection = myKeywordQuery.Execute();

ResultTable searchResultsTable = resultsTableCollection[ResultType.RelevantResults];

Ondorioz taula informazio zutabeak honako hauek izango dute: 

WorkId
Oharpenak
Izenburua
Egilea
Tamaina
Bidea
Deskribapena
Idatzi
SITENAME
CollapsingStatus
HitHighlightedSummary
HitHighlightedProperties
Contentclass
IsDocument
PictureThumbnailURL
ServerRedirectedURL

Zerrenda honetan eratorritako dut SharePoint batetik 2010 ingurumena, Enterprise Edition.  Zorionez egongo etorkizunean norbait erabilgarria izango da.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin

Arrazoigatik: "Huts egin du Erantsi fitxategi ateratzeko, irtenbide”

Bisual bat estudioa web parte proiektuan, gaur egun, berriz, lan-, Txiki fitxategi batzuk berriro org _layouts karpeta bat izango da jarri inplementazio-prozesuaren zati gisa egin nuen. Zehazki, . Js fitxategi bat izendatu zuenean naiz "TypeAhead.js" to "TypeAhead(zaharrak).js "  Kendu bezain laster, bere oinordekoa "TypeAhead.js" gisa frogatzen zuzena egiteko asmoa dut.  Begiratu duela dirudi:

image

Hau berehala eragindako estudioan ikusmen arazoren bat denean, proiektua hedatzen saiatu naiz:

Error occurred in deployment step ‘Add Solution’: Huts egin du fitxategia erantsi ateratzeko irtenbidearen.

Bihurtzen da behar ez duzula jarri fitxategi izenak parentesi bat.  Parens kendu nuen, eta arazoa konpondu.

</amaiera>

Nire blog Harpidetu.

Follow me on Twitter http://www.twitter.com/pagalvin