What is the difference between an Activity Feed's "Target" and "To" fields?
Can I use "Target" and "To" interchangeably? If not then what happens if I do use Target and To interchangeably? How does it impact my data and view?
Also, can I have multiple "Target"s?
The "target" field is just a supplemental field for noting that an activity is meant for another user/list, but it's purely a reference only and the field is optional.
The "to" field will actually send your activity to other feeds, like the CC function of your email client. It's also optional but we'll include an empty list in activities when you fetch a feed.
Related
How can I add hidden text fields or values into a document?
I have to receive documents and update a database with certain values. I want to add hidden fields into a document so that I could access the values when I get the envelope. How can I do that? The hidden fields I found in the documentation were focused on hiding sensitive data from a receiver. I want the field to be completely hidden.
You can use custom fields.
Custom fields are meta-data, hidden values that are associated with an envelope and you can use API to get/set them.
They are text fields limited to 100 characters, but you can have as many of them as you need.
Meta-data can be added at the envelope, document, and/or recipient (signer) levels.
Envelope-level meta-data can be optionally shown on the certificate of completion.
Here's a live API example that demonstrates use of the different types of meta-data while creating an envelope
We have several templates that take advantage of using same named labels to populate the data entered in one field to others with the same label throughout envelope documents.
According to API method Envelopes::EnvelopeRecipientTabs, in order to make this work via the API, I needed to add \\* (two back slashes) prior to the label name so that data pushed to a field would populate all and not just the first occurrence of a field with that label.
example: "tabLabel": "\\*Contract_Number"
This seemed to do the trick.
However, now I'm finding this works like a wild card. I have another field labeled "existing_contract_number" and the data for \\*contract_number populates this field.
I know I can change the name of the field so that the ending doesn't match, but there are many fields and many templates I will need to sift through to see if this is an issue elsewhere AND to fix this particular occurrence.
Is there something I am missing? Can I get the data to populate in all fields that exactly match the tabLabel without using essentially a wildcard?
Thank you.
I suggest listing the template's tabs or the envelope's tabs using a method such as EnvelopeRecipientTabs::list -- Note its include_anchor_tab_locations query parameter if you're using anchor tabs.
Once you have the entire list of tabs, update the values of just the desired tabs.
This may be more work than changing the template but will probably be a more generalized solution for your app.
I have a requirement where i should display the details(values) of the custom record in the suitelet sublist.
Now i have to create a custom Record with two fields. One field would be bill payment and other field will have list of bills related to bill payment.
When i create a custom record what should be my field vaues's type?
Appreciate any help.
I would suggest to keep one field of type List/Record and Record option to "Transaction", and second field of type Multiple Select with record option to "Transaction".
Since, the fields can hold reference to any transactions I would recommend writing a user event script which would fire on create/edit and validate that the fields value are always correct.
I need the end user to select which field he wants updated. Is there an option to have a lookup input parameter that let's the user select a field of the current entity?
I need it to perform operations on the value of the selected field.
As far as I know there isn't a custom type to handle a list of fields (or a list of strings) as InputParameter for a Custom Workflow Activity.
The (ugly) alternative is to use a string parameter where the user enters the field name.
If the list of fields isn't very big, you could add an optionset to the form with those field names and then your workflow could have If conditions based on that optionset.
I strongly suggest you to use a dialog to complete this. You can set the stage, the parameter and based on the situation the values to insert. Also you can execute workflows from the dialog itself.
If the record already exists, consider registering a plug-in on the update message. When in update the request InputParameter["Target"] contains only dirty fields changed by the user.
Instead of creating a list of fields you can create another (role) form to limit the fields the user can edit on the form.
I want to add new field on my custom form.
It should be 'Lookup' type and with target record type 'Email template'.
By default, CRM 2011 doesn't contains this entity in target records list.
Any suggestions?
Thanks!
I don't think you can do what you are looking for in that manner. If your goal is to ultimately send and email using the template you would have selected in your Lookup, you might try replacing it with an Option Set with values relating to your templates. Then in a workflow, you could check which item was selected in a Check Condition and then for each call the Send Email action specifying the template that corresponds to your selected value.
We have the same requirement for a client and managed to solved it. We built a Silverlight control that shows all the email templates and when clicked, it saves the GUID of the Email Template into a string field.
When the process runs to send the email it converts the string back into the GUID to get the Template record.