Issue with Seed Value when importing a solution into another environment

[Guzzie]

Hello,

I have created a solution in an environment and within a table, I have created a column “RecordNumber” which is Autonumber.  The Autonumber Type is “String prefixed number”. The value is 2 for “Minimum number of digits” and 1 for “Seed Value”.

However, when I verify this column after import into a different environment, I see the value for the “Seed Value” has changed to its default value being 1,000.

Consequence:

The intended autonumbering is 01/02/03/…

With the imported solution, the autonumbering becomes 1001/1002/1003/…

Has somebody already encountered this issue?

[cchannon]

Yes, you are expected to update autonumbering fields when you import them for the first time. Subsequent solution updates/upgrades then do not overwrite the seed so they don't break your numbering continuity.

[nava0003]

I have the same issue, I use to able to set the seed value on the managed solution, but now it is disabled.  Not sure if Microsoft has modified this capability on PowerApps. I did notice that the Advanced - managed properties now allows us to specifically "Allows Modifications" on tables and column entities, and we've tried re-importing the managed solution with this enabled.  But it's still does not allow us modify any properties, including the seed value for the auto-number field.  I have a support ticket in with Microsoft right now, if resolved I will post here. 

[Hemzi-fcc]

Did you happen to resolve this issue?

[DSchneiders]

Issue also occurred while deploying our managed app to our "production" environment. Does someone has a solution? 

[Hemzi-fcc]

my bandaid fix was doing a double patch...

  UpdateContext(
        {
            scr_patchRequestResponse: Patch(
                'Purchase Requests',
                Defaults('Purchase Requests'),
                {
                    cr553_author: gbl_UserExtended,
                    cr553_author_name: gbl_UserProfile.FullName,
                    cr553_email: Lower(gbl_UserProfile.Email),
                    cr553_author_email: gbl_UserProfile.Email,
                    cr553_date_created: Now(),
                    cr553_required_date: date_prf_form_date_required.SelectedDate,
                    cr553_description: txt_prf_form_requestDescription.Text,
                    cr553_total_sum: Value(txt_prf_request_sum.Text),
                    cr553_reporting_unit: Value(cb_prf_form_reportingUnit.Selected.Title),
                    cr553_special_routing: dd_prf_form_requestType.SelectedText.Value,
                    cr553_current_assigned: Lower(var_action_assigned),
                    cr553_status: "Requested",
                    cr553_file_url: scr_spUrl
                }
            )
        }
    );
    UpdateContext( /* THIS IS A DUCT TAPE FIX, INDEX OF UNIQUE_ID IN TABLES IN SOLUTIONS ARE RESET TO 1000 WHEN 
    THE SOLUTION IS INITIALLY IMPORTED. THE INDEX CAN'T BE ADJUSTED IN MANAGED SOLUTIONS.*/
        {
            scr_patchRequestResponse: Patch(
                'Purchase Requests',
                scr_patchRequestResponse,
                {request_id: Text(Value(scr_patchRequestResponse.request_id) + 106500)}
            )
        }
    );

[nava0003]

Yes,  Microsoft Support helped me out on this one.  I had to create an alternate unmanaged solution (for support purposes only) and manually added  to this solution the existing entity (table) with the 'autonumber' column that I want to manage the seed value for.  Then I saved and published this solution with the new seed value for this column that I wanted, and it worked.   I keep the solution handy now for support purposes only to make changes to the managed solution when required.  Hope this helps.

[thomst08-mahony]

Just updating this old thread for anyone who encounters this issue in the future.

The solution @nava0003 suggested works.

I have created a new production environment with a managed solution with a head of tables, this solution is a setup of tables form a development environment.  The seed numbers for all autoincrementing rows are at the default value (1000), however, I need to import data into these new tables and need to change the number to start at a different value.

I setup a new solution with the tables that need their seed number changed.  I then export this as an un-managed solution then imported it into the production environment.  I was then able to open this new solution and change the seed value for each table.  I then deleted the un-managed solution from the production environment.

This updated the managed tables and now all the seed values I needed to change are on the correct value.  No data was lost, and the tables are in a managed state still, I have also updated the managed solution that the tables are connected to with no issues.  Creating new rows also starts at the new seed value as expected.

[sean_dv]

Thank you so much @nava0003 and @thomst08-mahony !! 🙏 This worked for me.

I encountered the same issue and was so frustrated by it. I built a new app, to replace an existing spreadsheet. I had no way to know what to set the seed value to, until I had the managed solution in Production ready to go 'live' and imported the existing data.

I wish there was an easier way to change the seed value in a managed environment, but this workaround is amazing! 

[nmangueira]

Hello all,

Based on @nava0003 solution, you may do it straight in target environment:

1) Create a "dummy" solution
2) Add existing table (Seed value column only)
3) Edit column seed value
4) Save and Publish all customizations
5) Delete the "dummy" solution
6) Check