Trouble Importing UDF Values in Requests? Refer to This Format!
If you are facing issues while importing UDF (User Defined Field) values during request imports, kindly refer to the format shared below and ensure your data follows this structure for a smooth import.
Tip: Double-check that field names and values match your configuration exactly.
We recommend using this format for reliable results. If you have any questions or continue to face difficulties, feel free to reply here or contact our support team.
Field Type | Single Line | Multi Line | Picklist | Radio Button | Multi Select | Check Box | Decimal | Currency | Percentage | Numeric | Phone | Web URL | Date / Time | Decision Box | Lookup Field | Lookup Field (User) | |
Sample Value | John | John | John | John | [“John”, “Roger”] | [“John”, “Roger”] | 12 | 12 | 12 | 123 | +91 1234 Extn 12 | 01/01/01 | TRUE | California | |||
Column Value Type | Text | Text | Text | Text | Array Of Strings | Array Of Strings | Decimal | Decimal | Decimal | Numeric | Text | Text with Proper Format | Date / Time | Text with Proper Format | Boolean | Text with valid data | Text with Valid Data |
Remarks | Should satisfy the defined constraints if any | Should satisfy the defined constraints if any | Value should already be available in the picklist values. Special Characters not allowed except Hyphen and @ | Value should already be available in the Radio Button values. Special Characters not allowed except Hyphen and @ | Values should already be available in the Multi Select values. Special Characters not allowed except Hyphen and @ | Values should already be available in the Check Box values. Special Characters not allowed except Hyphen and @ | Should satisfy the defined constraints if any | Should satisfy the defined constraints if any | Should satisfy the defined constraints if any | Should satisfy the defined constraints if any | Can be Alpha Numeric | Should be in proper format like protocol://server | Need to select the proper date format during import in the SDP Cloud import wizard | should only be true or false | The value should already be available in the looked up entity. Example is the lookup field entity is Site, the proper Site Name should be in the Column | The email should be already be available as Technicians or Requesters in SDP Cloud Application before importing |
New to ADSelfService Plus?
Related Articles
Why Are Some Old Requests Not Visible in the Active Request List?
If you're unable to find certain older requests in the Active Request list view, they may have been archived based on your organization's data archival settings. How to Check for Archived Requests: Navigate to the Requests module. Click the Request ...Import Issue: Requests Are Being Created with Today’s Date
If imported requests are appearing in the application with today’s date instead of the original request date, please review the following: For import guidance, refer to this article: ? https://help.sdpondemand.com/data-imported Steps to Resolve the ...Move Requests Between Instances
ServiceDesk Plus Cloud allows you to move requests from one instance to another instance. For example, if you have a request that has been erroneously logged into your IT help desk, you can move it to your preferred instance, say, Facilities, without ...Business Rule Troubleshooting Guide
Refer to the following link for a scenario-based automation guide specific to Business Rules: ? https://pitstop.manageengine.com/portal/en/kb/articles/business-rule-scenarios Steps to Effectively Troubleshoot a Business Rule: Check if the Business ...Troubleshooting Slowness in SDP Cloud: HAR File & Network Trace Guide
SDP Cloud Performance Issues: What to Share with Support If you are experiencing performance issues in ServiceDesk Plus Cloud, sharing the right information with our support team can help us diagnose and resolve the issue faster. Please go through ...