UUID / GUID Generator

v4 or v7?

UUID v4 is 122 random bits: unguessable and universally supported, the same thing Guid.NewGuid() gives you in .NET and UiPath. UUID v7 puts a millisecond timestamp in the first 48 bits, so ids sort by creation time. That makes v7 the better choice for database primary keys and queue item references, because inserts land at the end of the index instead of scattering across it. Both are valid GUIDs wherever a GUID is accepted.

Common use cases in RPA & automation

• Unique Reference values for Orchestrator queue items, so a retry never collides with the original
• Correlation ids passed through an API call chain and written to logs, so one transaction can be traced end to end
• Temporary file and folder names a robot creates in parallel runs, with no risk of two jobs overwriting each other
• Test data: bulk ids for seeding a queue, a spreadsheet or a mock API
• Checking that an id coming from a form or a legacy system is a real GUID before using it in a lookup

The same thing in UiPath and .NET

Guid.NewGuid().ToString()        ' 3f2504e0-4f89-41d3-9a0c-0305e82c3301
Guid.NewGuid().ToString("N")     ' no hyphens
Guid.NewGuid().ToString("B")     ' {braces}
Guid.CreateVersion7().ToString() ' .NET 9+, time-ordered
Guid.TryParse(input, result)     ' validate