Module CustomFields Cases - Revision history

PolyglotBot: Import interlang links (links to translated versions of this page in other languages) from Multi Language Manager table.

2019-07-23T13:20:58Z

Import interlang links (links to translated versions of this page in other languages) from Multi Language Manager table.

← Older revision		Revision as of 13:20, 23 July 2019
Line 1:		Line 1:
			<!-- BEGIN origin interlang links -->
			<!-- You can edit this section but do NOT remove these comments
			Links below will be automatically replicated on translated pages by PolyglotBot -->
			[[fr:Module_CustomFields_Cases_FR]]
			<!-- END interlang links -->

	[[Category:CustomFields]]		[[Category:CustomFields]]
	{{TemplateDocDevEn}}		{{TemplateDocDevEn}}

Lrq3000: /* Cascading */ Added images

2015-04-01T14:22:58Z

Cascading: Added images

← Older revision		Revision as of 14:22, 1 April 2015
Line 209:		Line 209:
	1- Create a custom field "soccpy_nom" constrained on llx_society that will duplicate the society's id. This is necessary because other custom fields can only be cascaded using other custom fields, not any Dolibarr fields. Using duplication allows you to duplicate any Dolibarr field (and even $_GET and $_POST), so that you can use them to cascade. Copy the parameters as shown in this image:		1- Create a custom field "soccpy_nom" constrained on llx_society that will duplicate the society's id. This is necessary because other custom fields can only be cascaded using other custom fields, not any Dolibarr fields. Using duplication allows you to duplicate any Dolibarr field (and even $_GET and $_POST), so that you can use them to cascade. Copy the parameters as shown in this image:

			[[File:Cf-case-cascade-contacts1.png]]

	2- Create a custom field "contact_firstname_lastname" with Cascade option with parent "soccpy_nom" and constrained on the table llx_socpeople (the table of the contacts), which will show the list of contacts associated only to the selected society in soccpy_nom. Copy the parameters as shown in this image:		2- Create a custom field "contact_firstname_lastname" with Cascade option with parent "soccpy_nom" and constrained on the table llx_socpeople (the table of the contacts), which will show the list of contacts associated only to the selected society in soccpy_nom. Copy the parameters as shown in this image:

			[[File:Cf-case-cascade-contacts2.png]]

	And voila, you're done! The field soccpy_nom should be hidden so you won't see it, but you should see the field contact_firstname_lastname and you can check that only the contacts related to the society selected for the current invoice are shown.		And voila, you're done! The field soccpy_nom should be hidden so you won't see it, but you should see the field contact_firstname_lastname and you can check that only the contacts related to the society selected for the current invoice are shown.

Lrq3000: /* Cascading */ Added instructions

2015-04-01T14:20:38Z

Cascading: Added instructions

← Older revision		Revision as of 14:20, 1 April 2015
Line 199:		Line 199:
	= Cascading =		= Cascading =

			A simple example of [http://wiki.dolibarr.org/index.php/Module_CustomFields#Cascade cascading to select a location] can be found in the user manual.

			But you can do a lot more with cascading if you combine it with other options, such as Duplication and Hide. Here is an example:

			Let's say that in invoices, you want to be able to select a contact of the society selected for this invoice. Of course, you want that the list of contacts show only the contacts related to the society (ie: that you added on the Third-Party datasheet of this society).

			To do that, you have to proceed in two steps:

			1- Create a custom field "soccpy_nom" constrained on llx_society that will duplicate the society's id. This is necessary because other custom fields can only be cascaded using other custom fields, not any Dolibarr fields. Using duplication allows you to duplicate any Dolibarr field (and even $_GET and $_POST), so that you can use them to cascade. Copy the parameters as shown in this image:


			2- Create a custom field "contact_firstname_lastname" with Cascade option with parent "soccpy_nom" and constrained on the table llx_socpeople (the table of the contacts), which will show the list of contacts associated only to the selected society in soccpy_nom. Copy the parameters as shown in this image:

			And voila, you're done! The field soccpy_nom should be hidden so you won't see it, but you should see the field contact_firstname_lastname and you can check that only the contacts related to the society selected for the current invoice are shown.

	= Overloading functions =		= Overloading functions =

Lrq3000: Add section Cascading

2015-04-01T14:10:52Z

Add section Cascading

← Older revision		Revision as of 14:10, 1 April 2015
Line 196:		Line 196:
	* Cron job		* Cron job
	* CustomFields's overload functions		* CustomFields's overload functions

			= Cascading =



	= Overloading functions =		= Overloading functions =

Lrq3000: /* Static condition */

2015-02-24T16:03:15Z

Static condition

← Older revision		Revision as of 16:03, 24 February 2015
Line 164:		Line 164:
	=== Static condition ===		=== Static condition ===

			* Constraint WHERE clause (when creating/editing a custom field, you can specify your own WHERE conditions).
	* View: create a view on the table based on the condition, and then create a custom field constrained on this view (which is just like any table), eg: only show third-parties that are suppliers:		* View: create a view on the table based on the condition, and then create a custom field constrained on this view (which is just like any table), eg: only show third-parties that are suppliers:
	<source lang="php">		<source lang="php">

Lrq3000: /* Dynamic condition */

2015-02-24T16:02:30Z

Dynamic condition

← Older revision		Revision as of 16:02, 24 February 2015
Line 187:		Line 187:

	* CustomFields's Cascade Custom and Overload functions		* CustomFields's Cascade Custom and Overload functions
			* Recursive Remote Fields Access
	* Making your own module, which calls the CustomFields class		* Making your own module, which calls the CustomFields class

Lrq3000: /* Refresh the price instantly */ add an if statement

2015-01-16T14:14:20Z

Refresh the price instantly: add an if statement

Lrq3000: /* Refresh the price instantly */ Add javascript instant refresh code + more infos about commercial proposals

2015-01-16T13:41:12Z

Refresh the price instantly: Add javascript instant refresh code + more infos about commercial proposals

@@ Line 504: / Line 504: @@
 function customfields_field_aftersave_facture_global_coefficient (&$currentmodule, &$object, &$action, &$user, &$customfields, &$field, &$name, &$value, $fields) {
      // Force refreshing total price
-     $object->parent_object->update_price(0, 'auto');
+     $object->update_price(0, 'auto');
+}
 </source>
@@ Line 512: / Line 512: @@
 However, you will still notice one last glitch: when you edit the global_coefficient, the total price isn't reflected instantly, you must refresh the webpage once to see the new price. This is because of how the datasheet and the CustomFields hook are designed: CustomFields is called only exactly where the custom fields are place, thus it is called after the total price, the margin and the remaining debt are printed. Thus, CustomFields updates the value of your custom field only after all those informations get printed, and thus it cannot modify them at this stage. That's why those information are out-of-date, and you must refresh the webpage once to get to see the latest values.
-There is nothing you can do about it. One way to fix that would be to modify how CustomFields save the custom fields, by moving this stage at the very top. However, this would need another hook, which should be called at the very beginning of the page loading, which should be made only for this purpose (PageLoading), and should be available in all modules supported by CustomFields in order to not break anything.
+There is a workaround for this: refresh automatically the webpage (but delete the POST data to avoid an infinite loop). You just need to use this overloading code instead of the one above:
 = Modify the total price PER product/service line with a coefficient (without tampering the discount) =

Lrq3000: /* Implementing the change of price in margin module */ Add a note

2015-01-16T13:37:28Z

Implementing the change of price in margin module: Add a note

← Older revision		Revision as of 13:37, 16 January 2015
Line 488:		Line 488:

	That's all, the price should be reflected in the margin. Just refresh the page to reflect the change.		That's all, the price should be reflected in the margin. Just refresh the page to reflect the change.

			Note that this modification '''needs only to be done once for all modules''', you then just have to create a custom field named "global_coefficient" in every module you want to apply this coefficient.

	== Refresh the price instantly ==		== Refresh the price instantly ==

Lrq3000: /* Implement the change of global price in most of Dolibarr (including remaining debt to pay and PDF and ODT) */ Added a note

2015-01-16T13:36:57Z

Implement the change of global price in most of Dolibarr (including remaining debt to pay and PDF and ODT): Added a note

← Older revision		Revision as of 13:36, 16 January 2015
Line 435:		Line 435:

	Done, now try to add/edit a product/service line, and the total price should be affected by the global coefficient.		Done, now try to add/edit a product/service line, and the total price should be affected by the global coefficient.

			Note that this modification '''needs only to be done once for all modules''', you then just have to create a custom field named "global_coefficient" in every module you want to apply this coefficient.

	== Implementing the change of price in margin module ==		== Implementing the change of price in margin module ==

← Older revision		Revision as of 14:14, 16 January 2015
Line 518:		Line 518:
	// Force refreshing total price		// Force refreshing total price
	$object->update_price(0, 'auto');		$object->update_price(0, 'auto');
	// Force refresh the page to update prices that were printed before the custom field aftersave was triggered		// Force refresh the page to update prices that were printed before the custom field aftersave was triggered (and only if not creating the object because then there's no need to refresh)
	print('<script type="text/javascript">window.location.href = window.location.pathname + window.location.search;</script>');		if ($action !== 'add') print('<script type="text/javascript">window.location.href = window.location.pathname + window.location.search;</script>');
	}		}
	</source>		</source>
Line 532:		Line 532:
	// Force refreshing total price		// Force refreshing total price
	$object->update_price(0, 'auto');		$object->update_price(0, 'auto');
	// Force refresh the page to update prices that were printed before the custom field aftersave was triggered		// Force refresh the page to update prices that were printed before the custom field aftersave was triggered (and only if not creating the object because then there's no need to refresh)
	print('<script type="text/javascript">window.location.href = window.location.pathname + window.location.search;</script>');		if ($action !== 'add') print('<script type="text/javascript">window.location.href = window.location.pathname + window.location.search;</script>');
	}		}

Line 540:		Line 540:
	// Force refreshing total price		// Force refreshing total price
	$object->update_price(0, 'auto');		$object->update_price(0, 'auto');
	// Force refresh the page to update prices that were printed before the custom field aftersave was triggered		// Force refresh the page to update prices that were printed before the custom field aftersave was triggered (and only if not creating the object because then there's no need to refresh)
	print('<script type="text/javascript">window.location.href = window.location.pathname + window.location.search;</script>');		if ($action !== 'add') print('<script type="text/javascript">window.location.href = window.location.pathname + window.location.search;</script>');
	}		}
	</source>		</source>