{"id":715,"date":"2019-10-09T16:18:17","date_gmt":"2019-10-09T21:18:17","guid":{"rendered":"https:\/\/linux.asberry.org\/blog_tech\/?p=715"},"modified":"2024-05-14T09:13:48","modified_gmt":"2024-05-14T14:13:48","slug":"tcc-referencing-a-user-defined-field-explicitly-in-an-import-file","status":"publish","type":"post","link":"https:\/\/asberry.org\/blog_tech\/?p=715","title":{"rendered":"TCC &#8211; Referencing a User-defined Field Explicitly in an Import File"},"content":{"rendered":"\n<p class=\"has-text-align-left wp-block-paragraph\">I ran across this and thought that it was odd. On a candidate import, instead of using the standard field Prefix, we were needing to target a user defined selection elements named Prefix. The error being returned was the following:<br><\/p>\n\n\n\n<p class=\"has-text-align-left wp-block-paragraph\">Error Detail:<br> Code: internal<br> Description: A general internal error occurred.<br> Reason: Relation &#8220;Prefix&#8221; not found for the entity &#8220;Candidate&#8221; in the product pack<br> The error occurred in the following step: Prepare Import<br> The corresponding code for this error in version 1.0 would have been: -1<\/p>\n\n\n\n<p class=\"has-text-align-left wp-block-paragraph\">It was odd because one is a field and the other a selection. The fix can be found in Doc ID 1047706.1 on the MOS. <br>Basically to explicitly declare a user defined field\/selection, you need to prefix CustomField: to the field name in order to specify you&#8217;re speaking of a custom field. So Prefix,Description becomes CustomField:Prefix,Description and the error is solved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Update:<br>This post isn&#8217;t as clear as it should be so here&#8217;s a better example. Let&#8217;s say you have a custom field in experience that&#8217;s called ReasonForLeaving. This is a custom field that is the same as the standard field called ReasonForLeaving. The reasons why it&#8217;s named the same are not important what is, is calling the right field:<br>Standard field would be:<br>TalentUser,Profile,Experiences,ReasonForLeaving<br>Custom field would be:<br>TalentUser,Profile,Experiences,CustomField:ReasonForLeaving<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">So make sure the &#8216;CustomField:&#8217; declaration is for the field and not the reference location.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><br><\/p>\n","protected":false},"excerpt":{"rendered":"<p>I ran across this and thought that it was odd. On a candidate import, instead of using the standard field Prefix, we were needing to target a user defined selection elements named Prefix. The error being returned was the following: Error Detail: Code: internal Description: A general internal error occurred. Reason: Relation &#8220;Prefix&#8221; not found [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[13],"tags":[],"class_list":["post-715","post","type-post","status-publish","format-standard","hentry","category-tcc","author-aron"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p4bBkH-bx","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/asberry.org\/blog_tech\/index.php?rest_route=\/wp\/v2\/posts\/715","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/asberry.org\/blog_tech\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/asberry.org\/blog_tech\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/asberry.org\/blog_tech\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/asberry.org\/blog_tech\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=715"}],"version-history":[{"count":3,"href":"https:\/\/asberry.org\/blog_tech\/index.php?rest_route=\/wp\/v2\/posts\/715\/revisions"}],"predecessor-version":[{"id":795,"href":"https:\/\/asberry.org\/blog_tech\/index.php?rest_route=\/wp\/v2\/posts\/715\/revisions\/795"}],"wp:attachment":[{"href":"https:\/\/asberry.org\/blog_tech\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=715"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/asberry.org\/blog_tech\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=715"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/asberry.org\/blog_tech\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=715"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}