I am trying to figure out why/how certain fields are auto-populating on my Opportunity object when I complete a Docusign.
The issue: On an Opportunity record I click a custom button that sends a DocuSign to a list of signers. When the last signer completes signing the document, and the DocuSign Status is marked as completed I refresh the Opportunity record and 2 custom fields have been populated with today's date.
Here are the items I have already looked into to trouble shoot the issue:
On the fields themselves, I have clicked the 'where is this used?' button, and the only places these fields are used are in Page layouts and reports. It is NOT referenced in any apex classes or process builders.
I have looked through all my workflow rules, and field updates on those workflow rules. These fields are not referenced in any of the workflows/field updates.
I have set field history tracking on the fields and found that the change is being made by an integration user. I then set up a debug log on the integration user and in all of the debug logs there is no reference to the fields being updated there.
In a sandbox I tried deleting the field to see if it might be referenced by a Custom metadata type, and no errors were thrown saying it was. I have also looked into the custom settings and custom metadata types to see if the reference to these fields could be in there.
Hoping someone can let me know if they've seen this issue before, or know any other ways to troubleshoot this issue.
It sounds like there's been some custom configuration setup, out of the box the package shouldn't add new fields to the opportunity record that are updated upon completion of an envelope. All of that information should only be found on the DocuSign Status object initially.
I would recommend reaching out to the DocuSign support team and have them take a look at the configuration with you to see what may be happening. https://support.docusign.com/
Related
I have a newly deployed site running Dnn v9.10.02 and 2sxc v13.0.0. I am building a custom app that contains an Event entity and an Organization entity. One of the fields of Event is an entity type of Organization to mark which organization is hosting the event. When I try to delete an Event using the TagToolBar on the frontend I receive an error that it can't delete the entity. If I try to delete the same Event entity through the backend 2sxc panel the error message lets me know that the reason for the error is due to having an Organization entity as a child. If I remove the Organization child entity I can delete the Event using either the front end TagToolbar or the backend panel. Leaving the Organization in place while trying to delete the Event through the backend 2sxc panel I get the option to force delete the Event, which works as expected. Is there a way to ignore this error, or to at least get the force delete option, while using the frontend TagToolbar?
ATM this is not possible - for now on purpose, because simple users tend to hurt themselves by accident since they ignore these warnings and later blame the developer for the problem ;)
So ATM there is no direct plan to change this.
I found that Object History related list isn't supported in Lightning Experience : https://success.salesforce.com/ideaView?id=08730000000LgQWAA0 . I need to show it in Lightning; is there any way to show the Related History on Contact (in lightning) without creating a new object.
Thanks!
I tried to track few standard and custom field on Contact using Field History Tracking. In lightning, it doesn't seem to show the "Contact History" related list and its history records at all even if you add it to the page layout.
The only way I could do is to switch to "Classic View" and see the field changes in Contact History related list for the contact record.
If you need to see this working in Lightning, We will have to wait till the following idea (https://success.salesforce.com/ideaView?id=08730000000LgQWAA0) gets incorporated by Salesforce.
Update:
This has been delivered in Summer 17, for those who are still looking.
I am sending contracts from Sf using Docusign apis. There is information table in the document. I need to add editable form fields to document, so that the recipient can edit them to correct the information. Also I need to sense the changes made by recipient. Is this possible? If so, how to do it?
The functionality exists and it's called Merge Fields:
https://www.docusign.com/support/salesforce/documentation/dfs-user-guide/user-guide/create-merge-fields-user
Hope this helps
I am struggling to find where to start w.r.t my following problem.
In SFDC reports, there is an "export details" button to export a user chosen report into csv or xls formats. I want to modify this xls file (for example, encrypt it) before user downloads it.
I guess I can achieve this using Apex triggers. My questions are:
How can I add an Apex trigger which is triggered upon a user clicking this "export details" button?
How can I access the xls contents in this Apex trigger code where I want to encrypt them?
I extensively searched in Apex user guide and many other sources. I can not find how to add triggers to standard SFDC buttons.
Thank you very much in advance.
How can I add an Apex trigger which is triggered upon a user clicking
this "export details" button?
This isn't currently possible. First triggers are related to database actions and not user interface events. You can override the behavior for a lot of buttons using a view override, but unfortunately that's also not available for report buttons.
Workarounds
While you can't alter the behavior of the standard report experience, there is a new Reporting API that was just released by Salesforce that allows you to programmatically get the contents of a report. Using that you could build your own "encrypted report download" tool to accomplish this.
For more information, checkout this answer on Salesforce Stackexchange on accessing reports through the api. And in the future, post to Salesforce Stackexchange first!! That's where the community is these days ;)
Trigger can only be called when you do some dml operation in salesforce, clicking a button has no concern with the trigger calling,
I have been following the salesforce Recruiting App tutorial, and reached the section on creating a public site:
http://www.salesforce.com/us/developer/docs/fundamentals/Content/adg_composite_app_public_sites.htm
I have built a simple page to display open jobs as described here:
http://www.salesforce.com/us/developer/docs/fundamentals/Content/adg_composite_app_create_public_jobs_try_it_out.htm
This is displaying the open jobs correctly when I view it through our "internal" URL: https://c.ap1.visual.force.com/apex/PublicJobs
But when I view this same page through our "external" URL: http://servian-developer-edition.ap1.force.com/careers, the page still renders, except that now the list of jobs is empty.
I don't think this is a permissions error, as if so it would surely prompt me to log in. What do I need to do to make the data show on the "external" URL?
Make sure the "guest" user for the site has Read permission for the Positions object on its profile. You can't access the profile for the guest user through the normal Profile list page in Setup; instead, click on the Public Access Settings button from your site's detail page. On the profile, go all the way to the bottom of the page and make sure the Read permission is checked. If its still not working, ensure the Field Level Security settings also correct for that profile. The FLS settings are controlled about mid-way down on the same page.
In addition to above, ensure the object, if it is a custom object is in "Deployed" status. This fixed the issue for us.
Additional Information (from help.salesforce.com):
While developing a custom object or external object, you might not want users to see and interact with it. Because users might get frustrated with changes in layout or lose data when you delete custom fields, control visibility of the new object until you are finished.
Use the Deployment Status setting in the object definition to control when users can see and use the object and its associated custom tab, related lists, and reports.
Choose “In Development” as the Deployment Status when first creating your custom object or external object. Doing so hides it from users while you are designing and testing it. Only users with the “Customize Application” permission can see the object tab, search results, related lists, and report data types.
Change the Deployment Status to “Deployed” when you want to allow all users to use the object and any associated custom tab, related lists, and reports.
If you make more enhancements after deploying a custom object or external object, you can change the Deployment Status back to “In Development.”