Alex Chernov

Use this plugin to update an ACF field(s) when Gravity Form is submitted. You also can accumulate value in a certain field (only fields of type <code>Number</code> supported at the moment).
Features:
<ul>
<li>Target a wide range of WP entities: page, post, custom post, user, term, taxonomy, widget, comment, options page, current page/post.</li>
<li>Use GF merge tags in the ACF Target field</li>
<li>Simply map ACF and GF fields in one-to-one, one-to-many or many-to-many relations</li>
<li>Use operations on ACF fields to modify currently stored values</li>
<li>Number fields support +, – and * math operations</li>
<li>All text compatible fields support + operation to join strings</li>
<li>ACF field targets support merge tags</li>
<li>Implement complex logic with conditional feeds</li>
</ul>
Any GF field compatible with string/number values should work. Tested GF fields: Single line text, Paragraph Text, Drop Down, Number, Checkboxes, Radio Buttons, Website, Email. 
Any ACF field compatible with string/number values should work. Tested ACF fields: Text, Text Area, Number, Range, Email, Url, Password, Select, Checkbox, Radio Button, Button Group, True / False
Example use cases:
<ul>
<li>Count number of submissions</li>
<li>Remember name/login/email of the last user who submitted the form</li>
<li>Make a simple page like feature</li>
<li>Save name of a last sold product</li>
</ul>

ACF Feeds for Gravity Forms

Write Gravity Forms submission fields into ACF fields. Accumulate values over time.

John Huebner

Warning: Support for Sub Fields Removed as of Version 4.0.0
This is an add on plugin for Advanced Custom Fields (ACF) Version 5.
This plugin will not provide any functionality if ACF5 is not installed.
This plugin adds a field setting to all field types so that user roles allowed to edit the field can 
be selected. Only those roles selected for the field will be able to edit the field.
<h3>Github Repository</h3>
This plugin is also on GitHub 
<a href="https://github.com/Hube2/acf-user-role-field-setting" rel="nofollow ugc">https://github.com/Hube2/acf-user-role-field-setting</a>
<h3>Excluded Field Types</h3>
Most of the time it would not make sense for a tab field, unless all of the fields in the tab were set the same, in other words, removing a tab should remove all the fields in that tab. That’s not something that I can do at this point.
I’m not sure about the clone field, I haven’t worked with it much. You can test it out if you want.
I have also removed support for repeater, group and flexible content fields because I cannot preserver the values of these fields if they are not editable in the ACF interface. Please note that I do not know what the effect of allowing user role settings on these fields will be.
There is a filter so that you can adjust the types of fields that are excluded. Here is an example
<pre><code><?php 

 add_filter('acf/user_role_setting/exclude_field_types', 'user_role_setting_excluded_field_types');
 function user_role_setting_excluded_field_types($exclude) {
 /* 
 $exclude holds an array of field types to exclude from adding user role settings
 default value:
 $exclude = array('tab' => 'tab', 'clone' => 'clone');
 */

 // remove tab field from exclude
 if (isset($exclude['tab'])) {
 unset($exclude['tab']);
 }

 // add message field to exclude
 $exclude['message'] = 'message';

 return $exclude;
 }

?>
</code></pre>

ACF Feeds for Gravity Forms vs ACF User Role Field Setting