NW Chicago JavaScript Meetup: Overview of E2E Testing with Cypress – June 21

On June 21st PSCGroup will be hosting the NorthWest Chicago JavaScript Meetup in our offices from 6-8:30pm

We are very happy to announce a second speaker – Steve Schwarz !

In addition to the Firebase presentation this should make for a really interesting event 🙂

For more information check out the Meetup site

https://www.meetup.com/Northwest-Chicago-JavaScript/events/250983909/

Advertisements

Office Add-Ins: Working with Tables in Word. Part 2: Creation from OOXML

In this long overdue article I will discuss how to create a custom table, get the OOXML from it, clean it and then be able to insert the table anywhere into a Word document.

Background

In the previous article we looked at how to create a table from  scratch using range.insert table which is nice but limiting in that the formatting of the created table leaves a lot to be desired. It would be much easier to create the table we want first, get the OOXML and then be able to re-insert it pre-formmated so to speak.

Getting the OOXML of a table

One of the examples posted in the Add-in API documention uses the range.getOOXML to show how to extract the OOXML from a highlighted range in a word document. Using the Add-in Script Lab we can easily simulate this in a word document. I took the basic API call example and inserted the code from the API documentation.

 

  1. I created a custom table with hashed borders (formatting) and highlighted it
  2. Click the run code button to execute the sample code
  3. The OOXML was generated in the console below

Inserting OOXML

Using this process in reverse you can then copy the OOXML and using the range.insertOOXML method you can click anywhere in a word document and click a button to insert the preformatted table.

 

Conclusion

While we can format tables manually with code – as we get more complicated with out tables this may not be an option. Inserting as OOXML will guarantee the formatting we want and then allow us to manipulate as a table as we will see next

PSC Tech Talk: AI in Action – Azure Cognitive Language Services

In this short but interesting presentation Mark Roden and Jalal Benali talked about how they had used Azure Cognitive Language Services (Translation API) to elegantly solve a client’s need to have their intranet available in multiple languages across multiple territories.

Background

One of PSC’s clients has sites in multiple countries and as part of their intranet consolidation they wanted to provide a manner by which their corporate messages could be translated for the various countries/languages. The intranet was hosted on DotNetNuke CMS system and needed to be configurable, flexible and above all easy to use for the business. The business had looked at publicly available services like Google translate, but determined that on a private intranet site, they did not want any corporate information being taken outside of their control.

Azure Cognitive Language Services Translation API was selected as the solution because it is secure, private, easy to use and surprisingly flexible when it comes to converting web based content.

Solution

PSC created a custom module for DotNetNuke (DNN) which allowed content managers to create translated versions of the data at the click of a button. The solution was tied into the out of the box language capabilities of DNN whereby the languages available to the user for translation were those enabled in the DNN core configuration. In this manner if a new site, in a new country was purchased, the administrators need only turn on the new language for it to become available.

Because the Azure translations need to be reviewed for accuracy by a local admin in-country, PSC created the ability to have the new message held back for administrative approval. Once approved it is then published on the appropriate language version of the intranet.

Once the translations were created the global administrators would be able to monitor which ones were then subsequently modified by the local content manager. In this manner content corrections from the original English would not necessarily be translated and overwritten onto the newly corrected translated versions.

Limitations

  • The number of characters which can be translated at any one time is 10,000
  • No automated translation will be perfect, but for normal conversational English we found it to be better than we expected. For technical documentation the results were not as successful.
  • Some languages were better than others on the accuracy when they were reviewed by the testing teams in-country

Pricing

Depending on which service you use and usage, the pricing varies from free to $4.50 per million characters translated (as of May 2018).

Retention of HTML formatting

One surprising, significant, benefit of using the Translation API what that when fed an HTML string, the HTML tags were ignored. This meant that the formatting of the translation returned was identical to the original. While this does increase the size and number of characters translated, this would not approach the limits necessary for this effort.

Conclusion

The solution PSC implemented allowed the client to securely translate sections of their intranet and then manage the translated pages once they were published. Overall our experience with the Translation API was a very good one. We found it very easy to set up and simple the implement.

Cookies that cause Error 400 Bad Request when accessing Microsoft websites

For those people who interact with many sites across the *.Microsoft.com domain this may be an issue. I was looking for an update on Office Add-Ins and I came across this issue.

If you see a 400 Bad Request Size of a header exceeds the limit error, for no good apparent reason, that cause is likely cookies.

The following image was taken from just trying to access the Microsoft 365 Blog site. As you can see there are a LOT of cookies picked up from all over the MS domain.

The simple solution, clear your cookies. This process will vary per browser but once that is done, we are in business again.

 

NOTE

Microsoft is not the only company with this issue as I wrote about before 🙂

Office Add-ins community call

“The Office Add-ins community call is our quarterly event for developers to connect in real-time with the folks who are building the Office Add-ins platform and JavaScript APIs.”

The fact that we have a general office Add-in community call now is fantastic and shows how significant the community is to the product group.

The call was blogged and posted here: https://dev.office.com/blogs/office-add-ins-community-call-april-11-2018

The next Office Add-ins community call will be on Wednesday, July 11, 2018. You can download a recurring quarterly calendar invite at https://aka.ms/officeaddinscommunitycall.

 

Problems with Miracast? Could be a display adapter driver…….Solved

We use Miracast in the office to connect to the Tvs in the conference rooms. I used it for months without issue and then a few weeks ago it stopeed working for no good reason.

The display would say I was actually connected – and it would not come up on the TV. Eventually it would just die and tell me I had a problem.

After a considerable amount of trial and error it turned out to be the intel display adapter driver….ok then. Figured I should share.

  • Right click on the desktop
  • Display settings
  • Find display adapter properties

 

  • Properties
  • Update Driver

 

And after that and a reboot – Miracast back and working !!!