Has anyone customized the Map & Contact Bundle? (https://www.suiteapp.com/SuiteCommerce-Map-and-Contact-Info) Our current contact form is much more robust than what that offers, but I am unable to get it to work in 22.2. I am willing to cut out some of our current features to expedite this project and get a working contact page, but I still need the additional fields to have better/more options. Currently, a checkbox, date, email, integer, subtitle, URL, and text fields are all that’s offered. I need a drop down field. I am about to go look through the bundle code and see if I can modify this, but thought I’d check here, too. Thanks in advance.

Our official position is that you shouldn’t extend or modify any of the extensions that we provide. Of course, we can’t stop you (for example duplicating the code and making your own copy) but we also can’t offer support or keep it up to date for you

right, thanks. Well, there’s no support for why our current contact page won’t work in 22.2, so I’ll probably take my chances and try this.

@Melissa Did you ever get this sorted out? I would like to add a few addtional fields all of which must be drop-down list/record type.

@Suite Deal I did not. I had trouble adding a drop down field. Additionally, our current customization assigns cases to different roles, and sends a confirmation email. I can understand the roles part, but this suite app doesn’t even send a confirmation email. It’s pretty limited all around in my opinion for SCA’s “go-to” contact form. So, what I am currently doing is working on a re-write of our old customization. My biggest issue is why the

model.save

no longer works like it did on pre-TS versions of SCA. If I could get that to work, I think our old customization would be fine. Have you any experience getting that method to work in 22.2? Or have you experienced those kinds of inconsistencies?

No, unfortuantely, I'm just now being asked to scale-up for SuiteCommerce. I have many more questions than answers.

our migration from 19.1 to 22.2 has been a nightmare, and it’s not my first migration. Elbrus to 19.1 wasn’t fun, but it wasn’t this horrible. I’m not an SCA guru, but it seems increasingly difficult to work with. This migration and a couple other recent issues might be the tipping point that moves this org off SCA and to another front end

Ugh...sounds like a endless supply of rabbit holes.

It’s generally not that bad. I’m just unusually frustrated with this migration, and I’ve received conflicting info from support re: 22.2 that might have stopped this project before it got started. But overall until now I’ve enjoyed SCA mostly. I liked the older versions, like Elbrus the best. I develop less and less in SCA these days and more in NetSuite with SuiteScripts, so that probably plays into my frustration.

Up to this point, I've just been writing SuiteScripts. I must say, without guidance, it was a little challenging getting the Dev Tools working, as I was forced to run v.14.21.3. in order for a deployments to work. I'm stepping through the AnnoucementBanner demo. Made a bunch of tweaks, and now I can't figure out where the associated file is so i can remove/delete it from the Extension Manger list. LOL.

yeah the dev tools can be tricky, especially at first. When we migrated from Elbrus to 19.1 we moved every customization to the Extension Manger, switched the dev tools over to extension and theme dev tools. It was fine for 19.1 i guess. We ended up with 80 active extensions, which is ridiculous but it’s a highly customized site and industry. What I wish we’d done, is kept most of the customizations as extension.prototypes and overrides in the core. Which is how we developed in Elbrus. Back then, I was still pretty new to SCA, and thought doing that way just wasn’t going to be possible. With this migration to 22.2, I really wish we had it set up that way, without the Extension Manager. Way too many of our Extension just fail to work, way too many random Type Errors with no explanation. I’ve received conflicting info about being able to write TS in Extensions vs. core customizations with extension.prototypes. I am not sure setting it up the other way would have made this project easier, but I have a feeling it would have just from my JS experience. I know they say it’s compiled so it shouldn’t matter, but . . . nothing much works now. So, I tried to move everything over to core customizations, but I couldn’t get the distro.json file to compile and the documentation seemed out of date for 22.2 . . . so we’re back trying to stuff this migration into the Extension manager, and. . . it just really is bad.

Installed NVM so I could switch/test Node versions rapidly. After some trial and error landed on v.14.x. We do implementations, so we have like 5 clients running SuiteCommerce Standard. I think it's 2022.1

ah, ok. Defo some trial and error sometimes on dev tools.