First and Last Name should be a list Email - must be users email ID is a list
if the User provide value in one of the above and others fields should be auto populated.
@SaiPrasanth.Guthula
If all you need is the prefix of the email you can achieve this result using a system module using the Users as the only dimension.
Create enough line items to parse the email to get the email prefix as outlined by @DavidSmith in this post. @kavinkumar has a good suggestion too but the formula should be broken up to keep it simple.
If you want a cleaner way to obtain the email address based on first name and last name I would recommend exporting the User list and re-importing into your own user list (just the email prefix - don't use list properties). Then I would create a system module using that list and import the First Name, Last Name, and their formal email address. Then once the user enters their email prefix, everything will auto-populate because you're line items will be formulated to look them up from the system module.
Thank you @JaredDolich
Hi all, The Client ID and Client Secret are available, intended for uploading and downloading files. Could anyone advise how to use these credentials DIRECTLY to make API requests? Thank you!
I have A6 as the parent list and two sibling lists: A6.5 and A7. The A7 list includes an attribute that maps to A6.5. In the UX, the user will select A6.5 using a content selector, and the grid (dimensioned by A7) should display only the A7 items associated with that selected A6.5. Since the selector is a page context and…
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…