Anyone running into any weirdness using with a dem...
# ai-netsuite
b
Anyone running into any weirdness using with a demo account? I’ve been using SDF for about 6 months now, and I just started trying to test custom tools over the weekend, and I am running into what feel like circular problems.
didn’t want to throw up a wall of text but wanted to be as descriptive, thorough, and open as possible: 1. Project validates, project deploys - no errors, deployment log in NS UI looks clean 2. Can see tool - tries to run it and it fails right away - about 50% of the time it kills the connector too 3. My first test is just doing SuiteQL queries - I have verified I have permissions to the underlying records in netsuite UI, and the queries run fine in SuiteQL. 4. I am returning JSON and not raw data 5. I cannot find any error logs or any indication of what’s wrong 6. I have looked at very similar sample tools to make sure my syntax and general structure is consistent 7. Tried getting debug tips from both Claude/GPT - nothing pops out About ready to throw in the towel as I have already spent gobs of time I don’t have trying to make this work and seemingly getting nowhere. Only two ideas I have left: 1. something up with my demo account 2. I am making an extremely small, dumb error and no one is catching it (my eyeballs, a friend who is much stronger technically, all the AI tools I have access to) Where do I go from here?
r
Hey @Brandon Cumby try using the CFO role as a base and add MCP to this role and try Claude again
👍 1
🙌 1
b
@Ryan Longenecker thanks for the tip - that resolved some visibility issues with a handful of custom tools, BUT - the custom tools I created are still failing. I have deployed 3-4 sample tools with success, but the ones I created from a clean sheet of paper are still failing. I have stripped them back to almost no functionality, have tested the individual components (query works in SuiteQL in the UI), etc. - still get an almost immediate failure when I call the tool. It SURELY has to do with something small I am doing wrong. Where to check? I am happy to share everything if someone can help by pointing out where I am being dumb. At this point for embarrassment of making a bonehead mistake < banging my head against a wall any longer. 🤪
r
Hey @Brandon Cumby do your custom tools show up in Claude then fail or are they failing somewhere else?
b
They pass validation, deploy, and show up in Claude just fine - the second I call it - failure.
r
oh ok. I would assume it’s an issue in the JS or JSON file. Are you able to share those?
b
sure - please be gentle - I am a n00b
👍 1
in the latest plot twist - I simplified this JS this morning and the new function name is not syncing, even though I have restarted the MCP connection several times.
Originally I had it looking for Sales Orders at risk due to inventory stock outs so it was a lot more complex
r
e
@Brandon Cumby If the function itself if failing, you should be able to see your
Error executing supply chain query: ${e.toString()}
in Claude. In Claude does it show "Running `runSupplyChainQuery`"? If so, there should be a little box with an arrow where you can see the details of it running that function. Those details should show
Error executing supply chain query:....
Do you see any/all of that?
b
@Ryan Longenecker thank you! Is there a list permissions I can reference for future use? Also, does the xml differ if I am deploying as an ACP versus SuiteApp? Going to try this out a little later got pulled into client meetings this afternoon.
Validation failed. An error occurred during custom object validation. (customtool_supply_chain_tools_2) Details: The permkey field for the (permission) subrecord must not be TRANSACTION. File: ~/Objects/customtool_supply_chain_tools_2.xml 2025-09-03 122000 (PST) Installation FAILED (0 minutes 1 second) brandoncumby@15-inch-M3-Air test-customtools %
@ericbirdsall currently encountering errors (again) validating and deploying, but will reply back when I am on to that particular failure (again). round and round we go
🎠 1
successful deployment - cannot see tool - but the old one I nuked is still there
e
Disconnect the Connector in Claude and reconnect it
👍 1
You need to do this anytime you make any changes to the schema.json file OR if you add/remove deployments
1
b
Have done that multiple times in both desktop and web. I’m now convinced I’ve been fighting something else this whole time it’s just not apparent.