It appears that the ID value in the Participants Database is an arbitrary value created by the system and cannot be amended. This limitation makes the importing of WordPress users data very restrictive and would ask why you have this limitation (with regard to ID value) in place.
I’m using the Shortcode [pdb_record record_id=ID] but if the WordPress User id and Participants Database id’s do not match I have to resort to additional functions in order to obtain the required record. I’ve managed to do this using other functions, but it could be so much easier if the imported WordPress ID was used to create a new Participants Database ID so that the two fields matched.
In the Import Function you already have a drop-down with 3 options
1. Create a New Record with the submission
2. Update matching record with new date
3. Don’t import the record
What about a 4th option which would allow the WordPress ID values to be imported so that the ID values in the WordPress database match the ID values in the Participants Database.
If at some time in the future that you create a function or routine to align the Participants Database with the WordPress backend database, then surely matched id values will be an essential requirement. At the moment I have to export my WordPress users data and import it into the Participants Database which is a bit tedious. At the moment I do this on a weekly basis as I cannot see any other way of doing it. It would be so good if this was an automatic function.
Another possible solution would be if when using the [pdb_record] shortcode, I could use ‘username’ in addition to ‘record_id’ to locate my record. Both id and username are fixed ‘read-only’ fields which cannot be modified by the administrator.
Many Thanks