How to associate a SQL hrnet user correctly

Posted on August 14, 2008 by admin

The hrnet SQL user attached to the hrnet database is not synchronised with the hrnet SQL user correctly on the server

The following symptoms can occur:

1. When logging in to the HR.net web application the screen brings up a pop-up but the pop-up displayed just shows another log-on screen.

2. Error Message when logging in to the HR.net web application of
“Cannot open database requested in login ‘hrnet’. Login fails. Login failed for user ‘hrnet’.”

3. When attempting to associate the hrnet user with the hrnet database in SQL Enterprise Manager the following error is displayed, “Error 21002: [SQL-DMO]User ‘hrnet’ already exists.”

This is caused by hrnet SQL user assigned to the hrnet database is not correctly aligned / associated with the actual SQL user.

To resolve this issue Run the SQL script below on the hrnet database.

This script will re-align / re-associate the hrnet user on the database with the hrnet user on the actual SQL server.

sp_change_users_login ‘update_one’,’hrnet’,’hrnet’

Posted in SQL Server | Leave a comment

Message “The child record you are trying to save does not have any parent record.” when adding data.

Posted on August 14, 2008 by admin

Describes an issue that can occur when a save for a new record opened from a datagrid is attempted.

Message “The child record you are trying to save does not have any parent record.” displayed when clicking save on a new record created from a data grid.

This issue occurs because the new record is not aware of it’s Foreign Key.
This is a known issue that has been reported to development for resolution in a future release.

This issue, in most cases, can be resolved by modifying the ways that your screens/datasets are linked.

Take the following example:-
1. A screen is created with the main dataview as the Absence table (Child of People Table)
2. Contained on the screen is a datagrid that links to the Job Details table and displays jobs related to the People record selected.
3. It is possible to edit or delete Jobs displayed in the data grid but it is not possible to add new jobs due to the aforementioned issue.
4. Creating this screen in the following manner will resolve the issue:
Main Dataview = People
Two Datagrids – One related to Absence and one related to Job Details.

Posted in Admin Console | Tagged | Leave a comment

HRNET passwords being stored on users PC due to “Autocomplete for Forms” setting in IE

Posted on August 10, 2008 by admin

This is a security issue with Internet Explorer that can cause user passwords to be stored on a users PC.

When a user types in their user name into the HR.Net User Name dialog the password is automatically populated. This is a known feature of Internet Explorer which can be disabled on a per user basis or globally using a policy on the domain controller.  This issue has also been raised in Vizual as an enhancement request for the HR.Net software.

Per User Setting:

  1. Open Internet Explorer.
  2. Open Tools – Internet Options.
  3. Click Content tab.
  4. Click AutoComplete button.
  5. Disable the “Prompt me to save passwords” setting

If you have a domain of computer in your control, this feature of IE can be disabled via policy – refer to MSDN for full details

Posted in Web Appplication | Tagged , | Leave a comment

URL Label for Employee HR.Net Year Calendar not working when used on a workflow form

Posted on August 10, 2008 by admin

There is an issue that occurs when the ShowHRYearCalendar() javascript is used on a workflow form.

Using the javascript URL Label of

ShowHRYearCalendar()

on a workflow form does not display the standard HR.Net Year Calendar.  Using the same javascript in a screen works as expected.

This is a known issue and has been reported to Vizual development for enhancement in a future release.

While Vizual is trying to resolve this problem, It is possible to display the absence schedule calendar from a workflow form using the following javascript.

ShowAbsenceScheduleCalendar()

Posted in Admin Console | Tagged , , | Leave a comment

Database Writer using ‘System\New Key’ fails to write multiple records

Posted on August 10, 2008 by admin

There is an issue with the use of ‘System\New Key’ in a database writer when writing multiple records to the same table.

Database writer stage in a workflow uses ‘System\New Key’ to map to the primary key field of the target table. This will potentially be creating multiple new records in the table.
When the workflow is run, only 1 record is created, any subsequent records that should have been created by the same database writer stage do not occur.
No errors are reported, and the workfow appears to have completed successfully.

This occurs because ‘System\New Key’ is only generating 1 new key rather than 1 key per new record. The primary key value must be unique and as 1 already exists in the database it is unable to write the subsequent records.
This issue has been resolved in version 3.0.2.13156 by the addition of a new action type on a DB writer stage (Insert with New Keys)

*** Resolved in version 3.0.2.13156 ***

For HR.net version 3.0 onwards, use the “Insert with New Keys” option available on DB writer stages.

For earlier versions of HR.net, it may be possible to workaround this issue by redesigning the workflow such that the new records are written 1 at a time rather than in bulk.

Posted in Admin Console | Tagged | Leave a comment

Workflow stage is out of reach on the screen

Posted on August 9, 2008 by admin

When you have a very complex workflow and it is bigger than your screen, in older versions (before 3.0.2) of HRNET you won’t be able to access the stages sitting outside your screen.

Workflow stage is out of reach on the screen

Workflow stage is out of reach on the screen

This is a known bug in the system. It was fixed in the newer version, but if you are stuck with the old version, try the following ideas:

  1. Right click on the working area and select “Auto Layout” – sometimes it helps to rearrange the stages so you can reach everything. Personally, it does not work for me, so I prefer the second option.
  2. Run SQL Server stored procedure provided by Vizual: Move Stage Back On Screen. You need to open Query Analyzer for SQL Server, run the provided file – this way you install a new stored procedure on your database. Now, have you Admin Console open, but the problematic workflow closed, in Query Analyzer run the new procedure: SPOCSUP_MOVESTAGESBACKONSCREEN ‘WORKFLOW NAME‘. Where WORKFLOW NAME is your workflow’s name. Now open the workflow and see if you can get the access to the stage which was hidden before.
Posted in Admin Console, SQL Server | Tagged | Leave a comment

Page Break in Report

Posted on August 9, 2008 by admin

When you are making a report in Document Explorer, sometimes you want to make a page break just after your data grouping is finished.
For example, you are making a list of employees by departments and you want to start a new page every time department name changes. For this, in data source you need to choose table with employees, display names and department for each employee. It is a good idea to add sorting by employee name in the data source, but do not add any grouping there.
When it comes to the page layout, you need to select a grouping here:

Click "Grouping" button on top toolbar. Make sure you have selected the correct field for grouping. Do not add sorting, as it is already done in the data source.

Click "Grouping" button on top toolbar. Make sure you have selected the correct field for grouping. Do not add sorting, as it is already done in the data source.

This manipulation will create a grouping by the filed. To add the page break after the group finishes (or starts), you need to add “Page Break” element between GroupFooter and PageFooter:

Add a page break between GroupFooter and PageFooter

Add a page break between GroupFooter and PageFooter

Move PageFooter further down, so there is some space where you can put the page break. Page-break button is on top toolbar (see the screenshot): click it and draw a line in between the GroupFooter and PageFooter. It does not matter how big or small the break is – it does it’s job in any way.

Try the results you have. Once happy with the page breaking, you can make the page break as small as possible and remove the gap between the Page and Group footers.

Posted in Document Explorer | Tagged | Leave a comment