Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

newId cannot be found #38

Open
TonyVacha opened this issue Dec 2, 2022 · 9 comments
Open

newId cannot be found #38

TonyVacha opened this issue Dec 2, 2022 · 9 comments

Comments

@TonyVacha
Copy link

I have used this a couple time with no issues but now I am trying to convert a flow the source and the Destination are in the same domain but different sites which has worked before and I am getting the following error. I have done this same thing with others without this being an issue. Just not sure what is different in this case. Any help or suggestions I would be very grateful.
Thank you

ForEach-Object : The property 'newId' cannot be found on this object. Verify that the property exists and can be set.
At C:\Users\Public\Utilities\FlowConverter383\CompleteResourceMapping.ps1:19 char:10

  • $lists | ForEach-Object {
  •      ~~~~~~~~~~~~~~~~
    
    • CategoryInfo : InvalidOperation: (:) [ForEach-Object], RuntimeException
    • FullyQualifiedErrorId : PropertyAssignmentException,Microsoft.PowerShell.Commands.ForEachObjectCommand
@Zerg00s
Copy link
Owner

Zerg00s commented Dec 5, 2022

Hi @TonyVacha, sorry for the delayed reply.

I am not 100% sure what went wrong, but I have a few guesses. I any case, I think, I need to add a fix for a corner case you encountered.

Is it possible you could share a resourceMapping.csv file with me? I think resourceMapping.csv might contain a duplicate row with more than one copy of resource. If you do find two identical resources, then the error you posted makes sense.

@TonyVacha
Copy link
Author

TonyVacha commented Dec 5, 2022 via email

@Zerg00s
Copy link
Owner

Zerg00s commented Dec 6, 2022

hi @TonyVacha,

I don't think this file went through. Can you attach it via GitHub?

Denis

@TonyVacha
Copy link
Author

resourceMapping.csv

Ok Lets try this again

@Zerg00s
Copy link
Owner

Zerg00s commented Dec 6, 2022

It turns out that there are two views with the same name: /Lists/Nonconformities/PersonalViews.aspx

image

Can you delete the first occurance /Lists/Nonconformities/PersonalViews.aspx from the CSV file?

Or maybe, you can delete the CSV file and try running the migrator again?

If that works - I will have to update the script accordingly.

@TonyVacha
Copy link
Author

Those are actually two different Private/Personal Views that were created on the same list but they are named differently. But they both seem to show up in the resource file as Personalviews.aspx. I deleted one of the Personal Views and that fixed the issue and it ran correctly. I'm assuming that this will probably pop up again if there are ever people using personal views more. Luckily we just use them for testing.

On Another Subject have you looked at having this tool migrate the data from the lists to the destination as well?

@Centofanti
Copy link

@Zerg00s I'm attempting to migrate Power Apps SharePoint list forms from a test site to a production environment, and I'm getting the same issue. I'm noticing that I'm getting a lot of duplicate lists, and not all of them are personal views.

Could this be because my users embedded lists in web part pages? How do I get around this?

image

@Zerg00s
Copy link
Owner

Zerg00s commented Feb 3, 2023

hi @Centofanti . I am working on the new release. If things go well, I will have it ready by tomorrow (Saturday). I will post here soon with a follow-up.

Update
BTW, thank you for the screenshot! IT's always useful.

@Zerg00s
Copy link
Owner

Zerg00s commented Feb 3, 2023

hi @Centofanti , @TonyVacha . Thank you for posting the errors and screenshots. I have just released a new version: https://github.com/Zerg00s/FlowPowerAppsMigrator/releases/tag/3.8.4

It seems to be working fine, but if possible, can you check if your issue is also resolved in the new version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants