We've added the Generate Schema Report tool to ArcGIS Pro 3.2 and want to hear your feedback about it. I've posted a blog post to add context to the project with a brief history and also a look at where we'd like to take it in the future.
We know X-Ray was a much-used tool and hope this can help with some of the same workflows. Moving forward we'll be addressing a key workflow many of you have asked for: The ability to make schema changes in the Excel output and then reimport to create a new geodatabase with those updates. We're hoping to get this into Pro 3.3.
Generating a report of one dataset or a group of datasets (along with domains) is a very useful tool. However, the gdb x-ray tools real power is being able to alter the schema domain and reload it to a file or enterprise gdb. The only workaround I've found is use use FME from Safe Software.
Yep, agreed. This was the key workflow. As mentioned in the blog, updating the schema in Excel and reimporting to create a gdb with the changes is the next phase of this project. I'll add this info to this post here so it's clear that's where we're going with it.
I'd love to generate a schema report in the form of an Entity Relationship Diagram - ERD. If I recall right, Sparx Enterprise Architect can do it after importing a geodatabase XML Workspace Document. It would be proper to right-click the GDB and say, "make an ERD" as PDF or HTML format. Maybe there's already a tool for doing just that using the JSON or XLSX formats?
One thing I would love in the tool itself it the ability to over write the file that is created. This would help with automation, I did create a python file that kind of does that but it would be better if baked into the program.
I have three requests for changes to the output of the Schema Report tool, so I'll post them in three posts to make it clear. But firstly, I just want to say THANK YOU! This is great step forward. And it is good to hear that further improvements are on the way.
It would be great if the HTML report included a table of contents with links to each section (I think the XRay version used to have this?). In particular, I want to be able to click a link to jump straight to the Domains section, without having to scroll through, or do a search for it.
I've looked for training module to generate 'Flow' JSON scheme. While I have successfully built Flows with JSON it's more a hit and miss implementation. The principal reason my understanding at this moment in time is inadequate as to how to generate a schema correctly.
@CABIRD I totally hear you. When you have a chance, take a look at the PowerApps JSON function. It's actually so much easier to build your JSON in PowerApps and just send that as a single parameter to Flow.
The JSON schema doesn't have a File type. If the goal is to send info from PowerApps to Flow to create a file, at the 3:50 marker of Paul's video, you can see that File is of String type. Also at that point, you can see that he wraps in the File property from the Parse JSON action inside a dataUriToBinary() expression so that can be the file content. Please check out the screenshot I attached.
The issue is how do I generate the JSON scheme. The how is not explicitly shown in the video. Paul mentions running the Flow to generate the Scheme. However, you cannot generate output from PowerApp trigger and Initialise Variable alone to create JSON scheme.
I have built an app that works but that was tortious process to state the least as I had to build the schema myself. I have the Flow upload audio, files, photos, pdf metadata to SharePoint. I begin with a PowerApp trigger then my action initialise variable, then Parse JSON, SharePoint Create File, Update file Properties.
You can access and write data in repositories on GitHub.com using SSH (Secure Shell Protocol). When you connect via SSH, you authenticate using a private key file on your local machine. For more information, see "About SSH."
When you generate an SSH key, you can add a passphrase to further secure the key. Whenever you use the key, you must enter the passphrase. If your key has a passphrase and you don't want to enter the passphrase every time you use the key, you can add your key to the SSH agent. The SSH agent manages your SSH keys and remembers your passphrase.
If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "Checking for existing SSH keys."
If you want to use a hardware security key to authenticate to GitHub, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the OpenSSH 8.2 release notes.
RSA keys (ssh-rsa) with a valid_after before November 2, 2021 may continue to use any signature algorithm. RSA keys generated after that date must use a SHA-2 signature algorithm. Some older clients may need to be upgraded in order to use SHA-2 signatures.
When you're prompted to "Enter a file in which to save the key", you can press Enter to accept the default file location. Please note that if you created SSH keys previously, ssh-keygen may ask you to rewrite another key, in which case we recommend creating a custom-named SSH key. To do so, type the default file location and replace id_ALGORITHM with your custom key name.
Before adding a new SSH key to the ssh-agent to manage your keys, you should have checked for existing SSH keys and generated a new SSH key. When adding your SSH key to the agent, use the default macOS ssh-add command, and not an application installed by macports, homebrew, or some other external source.
Depending on your environment, you may need to use a different command. For example, you may need to use root access by running sudo -s -H before starting the ssh-agent, or you may need to use exec ssh-agent bash or exec ssh-agent zsh to run the ssh-agent.
Add your SSH private key to the ssh-agent and store your passphrase in the keychain. If you created your key with a different name, or if you are adding an existing key that has a different name, replace id_ed25519 in the command with the name of your private key file.
Note: The --apple-use-keychain option stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. If you chose not to add a passphrase to your key, run the command without the --apple-use-keychain option.
The --apple-use-keychain option is in Apple's standard version of ssh-add. In macOS versions prior to Monterey (12.0), the --apple-use-keychain and --apple-load-keychain flags used the syntax -K and -A, respectively.
In a terminal window without elevated permissions, add your SSH private key to the ssh-agent.If you created your key with a different name, or if you are adding an existing key that has a different name, replace id_ed25519 in the command with the name of your private key file.
Note: If the command fails and you receive the error invalid format or feature not supported, you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead.
Additional context
The Join Meeting dialog box saves meeting IDs but not passwords, so I would like to use a text file of meeting URLs so I can rejoin them easily. I have found nothing helpful by Web searching.
When you create a meeting, and configure it to require a password (on by default for Free, K-12, and Pro-single-user accounts), then it is returned in the Zoom Web Portal or Zoom Client. The same holds true for our API, if you Create a Meeting and configure the settings to require password, then the response object will come with the join_url property that has the full join URL you can share privately with your meeting participants.
That is too bad. So my understanding is that when a meeting is created, one can obtain a meeting link that contains an encoded password, but that one cannot create such an encoded password oneself (or, for that matter, decode the password from the encoded version in the URL).
I think this is a stupid limitation, since there is no security reason for failing to provide such a functionality. There are so many limitations in Zoom and especially in its Meeting interface, it is a wonder that it has been recently adopted so widely.
Technically, your use of bandwidth is excellent, and better than many of your competitors. You should leverage this ability, and transform your Meeting interface into something that people really want. You should stay ahead of your competitors, or else another company will do all this first and steal your entire market, as has happened to others.
This endpoint appears to retrieve meeting information only for those
who are authorized as creators of the meeting. I wish to generate full
URLs for meetings I did not create, for the convenience of combining the
meeting ID and password into one URL, as I indicated in my original posting.
I encountered this issue when preparing appointments for my children as they have just received meeting ID and password, but no link. It would make life easier for them if I just gave them the corresponding URL.
A generate rule can be used to create new Kubernetes resources in response to some other event including things like resource creation, update, or delete, or even by creating or updating a policy itself. This is useful to create supporting resources, such as new RoleBindings or NetworkPolicies for a Namespace or perform other automation tasks that may either require other tools or be scripted.
c80f0f1006