id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
24391	UUIDField with default=uuid4 triggers validation on otherwise empty inline formsets	Michael Angeletti	Tim Graham	"When using {{{DateTimeField(default=timezone.now)}}}, inline model formsets know to avoid validation when no fields are changed, even though there is a value in that given {{{DateTimeField}}}. However, when using another field ({{{UUIDField}}} in my case) I'm getting inline form validation on otherwise empty forms, presumably due to the default UUID being different than the one generated during POST.

This is at least related to #24377, but since this isn't constrained to {{{primary_key=True}}} cases, it needs its own ticket. Could a general solution to this render a specific solution to #24377 moot, or are they two separate issues?

== Digression ==

How does this {{{if user changed the default datetime value: count the form as having been changed}}} functionality work, btw? My understanding of dynamic default values like this is that there would be no way for Django to know whether the value has changed, unless the default value was included in a hidden field, or set in cache or cookies on page load... I'd love to document this, because if a user creates their own form field they might want to build in this sort of functionality."	Bug	closed	Forms	dev	Release blocker	fixed			Accepted	1	0	0	0	0	0