skuid/sfdx - process for deploying/pushing all of the pages
Hello
I just want to continue the discussion from this post: http://community.skuid.com/discussion/comment/20576507#Comment_20576507
How are you working around the limitations of skuid-sfdx for pushing and pulling pages along side of version control?
The issues I’ve identified are:
sfdx skuid:page:pull (and push I assume) has a limit of how much it can pull down before hitting an memory error. Meaning there cannot be too many pages in a module, or module cannot have too many big pages, and managing size of module is troublesome.
When pushing a page with a module that does not exist in the target org there are errors(?) or the page disappears, I don't remember, but it's another thing to manage: the module picklist is aligned.
If the module/name of the page has changed then skuid:page:pull will not override the old page, instead create a new one.
To handle few of those problems we’re thinking of not using modules any more. This will solve 2nd problem, and help with 3rd (page names co