Yeah, there isn't a ton. We did a lot via trial-and-error, by setting up projects with the settings we wanted, then doing GET queries to introspect how things worked and establishing patterns from there. It worked, though was definitely intensive.
I'm attaching a blueprint that you can import and test the functionality of the CSV create/parser mechanism. Hopefully this helps show you how it works. If you still have problems, I'd recommend creating an isolated scenario like this that reproduces and then post the blueprint here.Here's the ove...
Ensure your input file conforms to RFC-4180 (https://www.rfc-editor.org/rfc/rfc4180.html). This is the standard for CSV files and ensures what you're talking about is properly handled. Fusion's CSV parser is RFC-4180 compliant, and we import files like this all the time.
It appears to be a JSON encoding. You could likely do some testing and play with things to figure out how you'd want to do it. Appending would likely be as simple as just adding to the blocks array and republishing.(I haven't tested this, just speculating based on the structure that I'm seeing he...
Yes, if you have the report built, you can use the "Text Mode" variation to pull that in using <objcode>/report. It's a great way to leverage Reporting to build what you want and then the API to extract to other systems.
Pulling data from Workfront is going to be best done via a report or a search operation. Then aggregate that data into a CSV. Then upload to your downstream system.Here's an example using SFTP as a destination. You'd need to modify, of course, for your needs.(Standard disclaimer: not tested, use ...
This is how we do it, too, though via Google Sheets (sorry, Adobe). We also use LucidChart or other Visio-like tools for flow diagrams, UML sequence diagrams, etc. These are especially helpful for the Fusion scenarios.