Skip Navigation

NASIS Bugs and Known Issues

NASIS Client Version 7.0.3 - SVN Rev. No. 11713

These are NASIS issues that have been reported and you may want to be aware of them, but they were determined to be of a minor nature and difficult to change.

  1. An error message like “Object reference error” may pop up when closing a table editor. This is most likely to happen with a table that has a lot of child tables (like Data Mapunit) because it takes longer to close, and it happens when the mouse is moved around while the table is closing. You can ignore this message. (#108209)

  2. When using a tablet PC an on-screen keyboard normally appears when you start to edit a text field. This doesn’t happen with the new text edit pop-up box, so you will have to open the keyboard manually. (#81349)

  3. When viewing the Calculation table in the table editor, the column Base Table shows numbers instead of table names. Open the calculation editor to see the base table names. (#108220)

  4. Report output that appears in a browser can be hidden behind the NASIS window. (#106170)

  5. When you have messages in the status or validation list that include hot links, and you undock the message area, the links get changed to plain text. (#106734)

  6. When a NASIS data model change is made and you have left NASIS running on your computer, it will allow you to log in and continue working. But a download or refresh will probably fail due to the data model change. You have to exit from NASIS and restart, which will then force an initialization to the new data model. (#104154).

  7. When copying and pasting in text fields the Undo button may operate differently than you expect. Some inconsistent behavior has been seen (#106569).

  8. If a large number of editor tabs are opened, eventually an Out of Memory condition can occur, and a large red X will be displayed. At that point it is best to close and restart NASIS (#140229).
     
  9. There is an issue with NASIS dropping the locks on the server for checked out records in some instances. This happens when you exit NASIS without first uploading edits and checking in all your checked out data records. When you start NASIS the next time you will still see an “E” or “M” in the status columns indicating those records are still checked out. But those indicators are incorrect. The records are no longer checked out, however the local NASIS client thinks they are checked out and will still let you continue editing the data. If you refresh your local database those indicators will disappear, HOWEVER ANY EDITS YOU HAVE MADE SINCE YOU LAST UPLOADED CHANGES WILL BE LOST! If you do not refresh your local database, you will get an upload conflict if you try to edit the records and upload all changes.

    Solution:  Simply check out the record(s) again prior to doing a local database refresh, and then upload your changes.

    Best practices to avoid this situation is:

    • Before you exit NASIS, always upload all changes and check in all data.
    • Every time you start NASIS, do a refresh local database.
     
  10. Refresh local database is NOT refreshing data in your local database so that you can see edits made by other users. We thought we had a fix for this but it is not working. Until we can get a fix, the work around is this:

    • In NASIS, go to Setup Local Database
    • Find the data objects that you need to see refreshed data for. Highlight the row(s), click Exclude
       button, then click Accept button. This will remove this data object(s) from your local database.
    • Run query against national database to bring the data back into your local database.
    • Run query against local database to bring the data back into your selected set. Now you should see
       the updated data.