locked
VS2013 HTML Client: Converted from 2012; How to get the new auditing fields on the screens? RRS feed

  • Question

  • Hello,

    I've converted a VS2012 HTML Client solution to VS2013.  When I create a new VS2013 LS HTML Client project and create screens for new tables, I see some great auditing fields that are automatically added to the screens (i.e. last edit date, who did the edit, etc.).  In my converted application, I expected to see those fields added to my existing screens, but they are not there and cannot be dragged onto the screen.  Further, when I create a new screen in the converted application, these fields are not on the new screen.  So, I am wondering how I can add these fields to my solution.  I'd appreciate your ideas and suggestions.  At this point, we have too many screens to consider recreating them, so, hopefully, it is an easy matter to add them to existing screens.

    Thanks for your time and suggstions,

    Mike

    Monday, November 4, 2013 4:23 PM

Answers

  • In the data designer you have to ability to activate them:

    Note that you will have to redeploy your app, because the fields need to be added to the database tables.



    paul van bladel

    Monday, November 4, 2013 4:36 PM

All replies

  • In the data designer you have to ability to activate them:

    Note that you will have to redeploy your app, because the fields need to be added to the database tables.



    paul van bladel

    Monday, November 4, 2013 4:36 PM
  • Thanks for the great news and solution, Paul!  It was simple to enables those fields and then add them to our views...  Now, back to real work! :P

    Mike

    Monday, November 4, 2013 7:21 PM
  • Yeah, it's great that you can configure the audit logging on table level. The fact that you can disable it allows also to upgrade a VS2012 project without any database upgrade to VS 2013.

    It reminds me that my very first article I wrote about LightSwitch, which is about audit logs, becomes completely obsolete by this new built-in functionality :) { http://blog.pragmaswitch.com/?p=8


    paul van bladel

    Monday, November 4, 2013 7:28 PM
  • This is a good sign, Paul...  Our tools should make common features easier to implement, so we can focus our energies on the unique parts of our application.  LightSwitch is definitely moving in the right direction!  :) 

    Previously, we were creating MVC applications for our products, which required so much time and energy even for simple programs.  LS is our new standard because it is so extensible...  We have a solution that was created with LS, uses WebAPI for additional functionality, WebAPI + OData for some specialized data processing, and, of course, RIA.  It all works seamlessly together.  In a word, Wow! :D

    Monday, November 4, 2013 7:38 PM
  • Mike,

    Thanks for this spot on comment, 

    Of course, with LightSwitch there will be trouble also once in a while with a new release or whatsoever, but that's just part of the daily life of a software developer, if you can't stand the heat stay out of the kitchen.... but indeed, at least with LightSwitch we can focus to the max on adding business value to line of business apps.  Going the mvc way, still means 'de facto' rolling your own framework, and please can the first framework specialist stand up and say us that a new release always goes painless?  With the current state of affairs, mvc means being in constant maintenance mode, because every day new libs arrive and there will always be an alert developer convincing you to use them all....


    paul van bladel

    Monday, November 4, 2013 8:30 PM