InfoPath Dev

I'm transferring a form on 2010 SharePoint to Sharepoint 2016. but I have a NaN problem. I'm having trouble as I showed in the video on the link. https://www.youtube.com/watch?v=WZtCzv-PVoc

Can I see a copy of your form? You can attach it in a reply under the options tab.

I've added both forms. working and non-working forms are attached. Meanwhile, the language of sharepoint 2010 is English. The language of Sharepoint 2016 is Turkish.

My guess is that max(ID) returns a value in your old form because there are files in the library. If there aren't any items in the library, max(ID) + 1 will return not a number. If you use rules to set the field instead of a default value, you can work around that - add conditions for what to do if ID is not present.

When a new document is added, the number increases to "+1". how did this form generate the first number "01"? What should I do to continue counting? Can you look at the two screenshots I've added? I haven't added a document to the new library yet, so doesn't "NaN" generate numbers? If I move "xml" documents from the old library to the new library, will "NaN" continue to generate numbers?

Right. That's the behavior I'd expect. Max(ID) is now returning a number. When you move the old docs into the library, there will be IDs returned to the data source, so the formula should work as anticipated.

After moving the forms began to work where the number left, thank you. i:0#.w| These characters appear at the beginning of the domain and username field, how do I prevent them from appearing?

Your new SharePoint site uses Claims Authentication. That is a claims prefix. You should be able to use the substring-after function to remove them.

where and how can I make this change?

It really depends. You could display a calculated value using a formula that trims that off for display purposes. I see in one of the forms you sent me that the KullaniciAdi uses the userName() function as a default value - you could replace that with the substring-after function to trim off the unwanted chars.

I did as you explained but it didn't work.

In preview, your userName won't have the claims prefix. Are you checking it in preview or in the browser? Can you tell me what "doesn't work" means here? No result, incorrect result, etc?

it looked empty when I tested with a system account, but it seems to be improved when I try with a user account, thanks

Change the formula back and verify you have the prefix correct, I guess? You could also add a calculated value field that shows the result of the userName() function for testing - to make sure the prefix is right. Or you could use substring-after just the "|" char.

I corrected my previous message, thank you