query SQL Request Importer - Historic Updates - h_updateby, h_updategroup, h_actiontype and h_actionsource

[Martyn Houghton]

I am currently undertaking test migrations using the SQL Request Importer (v1.3.1), and I am trying to carry over a much information into the Historic Updates that the tool allows. Would it be possible to get some clarification on the below:-

• h_updatedby and h_updategroup, are these just literal values or are there lookups applied to them such as the User lookup and Team Mapping?
• h_actiontype and h_actionsource I am presuming these are textual literal values which we can pass in any text from the source system?
• h_timespent is passed in as an integer in the unit of minutes?

Cheers

Martyn

 

[Steve G]

Hi @Martyn Houghton,

Sure:

• Yes - literal values, just displayed against the Historic Updates in the request details form
• Yes - literal values, again just displayed against the Historic Updates in the request details form
• Yes - it's an integer field. This was based on the old Supportworks field of the same name, that stored its value in seconds. But, this could be used to store value in minutes as I don't think this is displayed on the request details page - it's more for reporting.

Cheers,

Steve  

[Martyn Houghton]

@Steve G

Thanks for clarifying.

Cheers

Martyn

[Martyn Houghton]

@Steve G

It would appear that updatedby does have a lookup on it as the import reports errors when I do not translate the user names.

Update is still added bu no user information is displayed.

Cheers

Martyn
 

 

[Steve G]

@Martyn Houghton,

Apologies, it's been a while since I looked at that code, forgot that I'd added those lookups. I'll update the tool to just write the user and team names to those columns if the lookup fails. Will let you know once it's done.

Cheers,

Steve

 

[Martyn Houghton]

@Steve G

Thanks for looking at putting the literal value on lookup failure.

Cheers

Martyn

[Steve G]

Hi @Martyn Houghton,

Those changes have been made, and I've just released v1.4.0 of the tool:

https://github.com/hornbill/goHornbillRequestImport/releases/latest

Let me know how you get on with this.

Cheers,

Steve

[Martyn Houghton]

@Steve G

Thanks. I doing a migration end of this week and start of next,so that will try inserting literal values for the people making historic updates.

Cheers

Martyn

[Steve G]

@Martyn Houghton 

Great stuff. I should also have mentioned, you can now add h_updatebyname to the mapping as so:

This allows you to populate the users name from your DB record when the user lookup fails.

Cheers,

Steve

[Martyn Houghton]

@Steve G

If leave the h_updateby as null, will it not both with the look up and just insert the value provided in h_updatebyname?

Cheers

Martyn

[Steve G]

@Martyn Houghton 

Yes that's correct. 

Cheers,

Steve