/build/static/layout/Breadcrumb_cap_w.png

Custom Field Update Rule changed in upgrade to K1000 7/8

We just updated to the latest version of K1000 server and I see the documents about the changes but I don't understand how to get my UPDATE query to work on my rule to add a site location-being pushed from AD. 
Can anyone provide a bit more guidance?
Here is what I have now (to add a site location-being pushed from AD):

SELECT HD_TICKET.ID AS ID FROM HD_TICKET 
JOIN USER S ON (S.ID = HD_TICKET.SUBMITTER_ID) 
WHERE HD_TICKET.SUBMITTER_ID <>0

Update Query:
UPDATE HD_TICKET T
JOIN USER S ON (S.ID = T.SUBMITTER_ID)
SET T.CUSTOM_FIELD_VALUE1 = S.LOCATION WHERE T.ID=<TICKET_IDS>

I see that the column is no longer located where it was but I cannot figure out the proper SQL syntax.  It seems to fail on the UPDATE Query according to the logs.

New Location of Custom Fields
(this is from the support document)
SELECT
  USER.FULL_NAME,
  ASSET.NAME
FROM
  USER
  JOIN ASSET on USER.LOCATION_ID = ASSET.ID

Thanks,
Jim

0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: civilnj 7 years ago
Orange Belt
0

Top Answer

SOLUTION:

Update Query

UPDATE HD_TICKET T
JOIN USER S ON (S.ID = T.SUBMITTER_ID)
JOIN ASSET A ON (A.ID = S.LOCATION_ID)
SET T.CUSTOM_FIELD_VALUE1 = A.NAME WHERE T.ID=<TICKET_IDS>

Figured out with some assistance.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ