usecase: let´s say you have a "booking" (form) with a number of X "booking amounts" (formset). now the user could be able to save a pre-defined template for common bookings. these templates are saved as "template" and "template amounts". so, if the user selects a given template, the template-amounts should be the "initial date" for the booking amounts.
maybe this is totally out of scope, I´m not sure. and maybe there´s another way to insert the template ... it just seemed very natural for me to use "initial" with an inline mode formset, till I figured out it ´s not possible. patrick. On Aug 19, 9:22 pm, "Brian Rosner" <[EMAIL PROTECTED]> wrote: > On Tue, Aug 19, 2008 at 12:10 PM, patrickk <[EMAIL PROTECTED]> wrote: > > > any reason, why it´s currently impossible to use "initial" with > > inlineformset_factory. is it planned to integreate this feature? > > I guess I am failing to see how this is useful? initial data in an > inline model formset is based on the queryset such as it is a subclass > of model formset. Could you provide a use case where it might be worth > it to also provide initial data for an inline model formset? It would > seem that a default value on a model field would be sufficient. Seems > a bit overkill for the general case due to the unknown size of the > queryset. > > -- > Brian Rosnerhttp://oebfare.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
