about locating all demand numbers

[BD5]

We are pulling ServiceNow tables directly into snowflake via Fivetran's ServiceNow connector. When data is loaded into snowflake, demand number, project number and task number in dmn_demand, pm_project and task tables
have values like '3f07eb768701dd900916b95f8bbb3564' instead of actual values of demands, project and task as in service now. When we look deep into other tables, project number are listed in pm_project_portfolio  or planned_task table but for demand number we don't find any table that has all demand number. Some of the demand numbers are in demand baseline table but don't why it does not contain all demand numbers. Does anyone have similar issues with demand numbers ?

[Carolyn Rast]

@BD5 autogenerated numbers can have gaps depending on how you load your data.  I frequently see gaps in numbers - for example I've been loading Business Applications (APM) via spreadsheet and the numbers sequential (no gaps) but the numbers on my Application Services (SNSVC), created manually, increment by 4.

[CMDB Whisperer]

Yes.  This is because the number is incremented before the record is committed.  So if you open a form with that number but omit the save, that number is gone and will never be used.  This also can work differently in scripted GlideRecord operations depending on whether you use the initialize()...insert() method or the newRecord() method.

[BD5]

Thanks for your help guys. I was able to figure out using u_initiative_number in dmn_demand table which actually refers to the demand number without DMN in the front.