Slate Spotlight on Suitcase with Carnegie, powered by Underscore

Alright, looks like we've got a ton of participants joining.

Just give it another minute just to let some folks join in and then we will get started.

Great, great.

Thank you all for joining us today. We're here with Carnegie Power by under score and joined by Megan and Emma who will be taking us through our slate spotlight on suitcase. I, Nita, will be your moderator today and we will hold all questions until the very end. So feel free to go ahead and post them out in the chats. I will keep an eye on those and we will return to answer all of your questions. And right now I'd like to turn it over to Megan and Emma.

I think you're muted, Megan.

Good start, I was going to say. I'm going to share my screen.

Alright.

So welcome to today's slate spotlight on suitcase with Carnegie powered by under score. We were pleased to be hosting the first in a series of several post summit new feature spotlights, during which you'll hear from preferred partners as we discuss a specific new feature announced at Summit and rolled into our databases since the conference.

My name is Megan Robinson, and I'm the executive Vice President of Slate strategy at.

On the slate optimization team within the Carnegie slate team.

I oversee the slate optimization team, which is 7 lines of slate strategy. Prior to joining the under score Carnegie team, I worked at my alma mater as their Communications Coordinator and Slate. Soon I fell head over heels for not just the communications tools but all of Slate and took my admissions counselor Coms role and grew into a full-fledged slate captain.

I joined them, then under score team as a communications strategist, founded the Implementation Division and now work to grow all areas of slate in my current role, one of which is still the implementations team. On to my colleague Emma.

Thanks, Megan. My name is Emma Hayek. I am a senior slate strategist with implementation and consultation. Which is kind of a way to say that I get to help various institutions either build out a new slate instance or use their slate instance better, more efficiently, build out projects that they might need some guidance with. So play in Slate all day. Essentially. I got into this by being a tour guide, turned into an admissions counselor, and we had implemented.

And I just fell in love with all that it could do and all the creative problem solving. My fun fact is that I like to use a laser cutter to make various items as a side hobby.

Thank you. I actually skipped over my fun fact, which is that I grew up on a quail farm in Indiana, so we both have a lot of fun things going on, on the side if you wanna chat about those later.

All right.

As I mentioned, today's combo is hosted by Carnegie powered by under score, which is our way of saying that the slate expertise you associated with under score is the same expertise powering the slate arm at Carnegie. You may have heard it summit, but we are now indeed officially the slate optimization team and I mentioned that my role is to grow our slate services. So for some context there.

The Slate Slate team offers 7 areas of slate strategy, implementations and consultations where we do from scratch implementations for enrollment, student success and advancement, populations, audits, general consultations and more, communications if you'd like to bring your search and house all the way through melt and all custom creative and reporting all within your instance. We offer portals, dynamic student or user based portals, trainings, whether on campus, virtual or in Charlotte if you'd like to visit our office on any module or for any audience.

Integrations whether SIS or maybe for CAS applications, document management systems and more reporting, whether funnel based year to date goal tracking or even maybe even reports within portals or reports. More to come in our November dive deeper and recruitment strategy. So engagement scoring, admitted student surveys, tell recruiting campaigns and more.

Not only does Carnegie have a powerful slate team, but there's so much more to our being the end to end higher education, marketing and enrollment partner for so many institutions between financial aid optimization, lead generation through college express, digital marketing, web development, psychographic segmentation. That is Carnegie in a nutshell. So why are we here today?

Today we're going to discuss suitcase functionality and why and how you may want to use it.

So what is suitcase exactly? We'll go through the actual definition of this new tool. What are some considerations that you should keep in mind before and while you're used? Suitcase? What are ways in which you can use suitcase? And not just some of the ones that automatically come to mind. But if you know Emma, she's super creative and thinking of new innovative use cases for suitcase and really any new feature as well. We'll go through some tips like what else you should know about suitcase just in general and close out with some resources whether articles, upcoming webinars and then go through some of your pre submitted.

Questions, or maybe even questions that come through come up throughout the conversation.

So let's get into it again. What is suitcase and what do I need to know before I use suitcase, including how to use it?

An excerpt directly from technicians suitcase is the bigger, better briefcase. It allows you to create customized, personalized packages that can include a variety of objects and be imported from another database, or maybe even across your own. They're personalized because not only can you select which items you want to bring in as a whole, but you can decide which parts of those items you want to import as well, leading to that personalized component.

So why enable suitcase? First, though it may seem obvious, it's worth reminding you that you should enable suitcase so you can start bringing in the ideas you're seeing in the knowledge base and in this latest news articles. Before doing so right this second, though, hang with us as there are a few things you want to consider before activating this early access feature.

Why else should you enable suitcase? Not only does suitcase naturally save you time as you bring in multiple customized objects from other instances, meaning you don't have to start from scratch and building these complicated objects, which is nice, especially if you've already done so in tests. But you can say you can even save time by copying a form within the same instance, because in suitcase that form logic comes over in the copy too.

And what we love almost as much as saving time is the further building of relationships within this like community. Who doesn't love seeing currently a briefcase code in an article or forum response from another slate user? But maybe with briefcase IDs? You might have been nervous to import those objects before, because you'd then have to build all the related pieces of the project and maybe find all the customizations from the previous instance and switch it to your own. But now you won't hesitate to bring in those ads you see a knowledge base, because with suitcase you can use expanded functionality to import all the pieces of a larger process and choose which of those packages.

Particular pieces you want to bring in and how that looks for your instance.

So now on to what you really want to chat about.

While all important, perhaps the most important is that one suitcase is enabled. You can't turn it off. So these are those things that we were talking about considering considering before you enabled suitcase.

This is actually the case for all new features activated through early access configuration, by the way. So this doesn't apply just to suitcase, but it is worth mentioning since that's what we're talking about today. This matters because briefcase is not compatible with suitcase and vice versa. Though we may have a short term recommendation involving briefcase into tests if test doesn't have suitcase enabled, but still that would only be a temporary solution.

Also, different from briefcase, suitcase requires the admin permission. This is an intentional change given that suitcase sharing is more comprehensive than briefcase. So technicians wants us to encourage to keep that permission a little bit tighter than we may have with briefcase.

All things considered, the move to suitcase should be an easy one as long as you have already briefcases all briefcase IDs into your environment. If you're ready to make the move, head to database, configuration keys, early access features, and check that box.

But now that it's on, you may be like, what now? As I mentioned, Emma's fantastic and is our residency suitcase expert. So she's going to walk us through just exactly how to use suitcase and what you might want a suitcase, Emma.

Thanks Megan. So first of all, how do you use suitcase? So if you are in an instance where suitcase has already been enabled, you might notice that the interface when you go to copy certain objects already looks different even if you're not going into build that full package of objects. So method, one of how you can use suitcase which works on select objects only is going directly into that object that you want to either create a new suitcase from or add to an existing.

Suitcase, so that would be kind of the replacement of where you used to see the copy to briefcase. Because they are mutually exclusive, you'll see copy to suitcase as your option. This will work on things that you would be able to copy to the briefcase originally, so things where you can save as copy and you see that option directly in the object. But you'll notice when you look through the full list of items that you can suitcase in, certain things kind of stand out to you of how would I get them?

Into the suitcase. So this works on select objects. Method Two will work on all objects of. How to get them into suitcase?

So method two, we're going to go directly into the suitcase module within database. So instead of starting in the object that you're wanting to move, we're going to go into suitcase. Then we're going to choose whether we're adding a new suitcase or adding to an existing suitcase. So here we're making a new example suitcase.

Then we're able to add new so we can add a variety of different objects in there. It doesn't all need to be formed within a suitcase. It can be a combination of a bot app logic, a form, a query, a report, all within that same suitcase. This is where you're really going to see that full list of objects that you would be able to bring in. So some you can pull in both ways, some like app logic, you can actually only pull in by going directly into the suitcase and adding that object into the suitcase.

As we talked through what can be suitcase, this is mostly the list from the Knowledge Base article. I actually split out a couple of the items in here. So queries absolutely can be suitcases, but so can query libraries. And to me that's a really important differentiation because you can't move a query into a query library. So the power that comes with being able to suitcase a query library technicians publish some commonly used and person.

The app scoped exports and filters as query libraries to kind of recreate what the slate template library had done. For us. To be able to pull that in and then use it across your instance is incredibly powerful.

You'll notice that as we talked about a bigger and more robust briefcase, there are certainly things in here that you wouldn't have been able to bring in with briefcase before. So not only is it expanded functionality with maintaining form logic and some other pieces that we'll we'll dive into in a little bit, you can also bring in different objects than you used to bring in with briefcase.

And I'll make a little tiny plug for query libraries. The reason why query libraries is amazing is you can use the pre built exports and filters across your instance. So if there's something really complicated that you've built in another instance or that you pull in from something that technicians has created, you're able to apply that in a rule, in a deliver mailing, in a portal, wherever you could use a configurable joins export or filter.

You'd be able to use those pre built pieces.

Now let's talk through some use cases. Let's get the wheels kind of rolling on how we might want to use suitcase. What does this expanded functionality do for us?

One of the use cases that we kept coming back to as we were thinking of the different areas that we can use this moving from test to prod, that's typically A1 way street, right? It goes from test or from prod into test. What if we built something in test and now we want to move it into prod?

It doesn't move everything, so we'll talk through some things that we can't move with suitcase, but it moves a lot of things. So being able to really test a process in its entirety and test and then say move that form or multiple forms with complicated logic in it into production without having to recreate it, and then potentially missing a step and trying to troubleshoot why it isn't working in production is going to save you a ton of time and headaches.

And as a part of the implementation team, one of our thoughts was reimplementation. There's a lot of work that goes into test in a reimplementation and there's some, some downtime, right? So essentially minimizing that downtime, but not actually having to rebuild everything in production, but being able to bring some of those pieces in and save you a little bit of time, which obviously not being down during a reimplementation is, is a huge piece.

G PA calculators who wants to build a GPA calculator from scratch when we have some great starting points out there? So there are some really good forms that have been shared either by technicians or by others in the Community forums that you can bring into your instance. That used to be true with briefcase right we could briefcase forms, but to have the logic work to be able to not have to tweak as many things once they come into your instance really saves a lot of time and.

And just improves on that briefcase functionality.

I think this is probably the one that we all maybe noticed if suitcase was enabled in our instance and kind of said wait a minute, just form logic, stay now. So to be able to make a copy of a form, say we have different iterations of event templates and we want to be static mapping to the school level of study if they're a freshman, but we want them to answer the question if they're a transfer student, we now don't have to go in and recreate all of that form field logic, even if it's not tied to a system field.

Campaign performance reports, or really a lot of different types of reports. Everyone I think who has been in reports knows that it is much easier to tweak or update a report than to start from scratch. So having at least a a somewhat solid starting point of the type of information that you're looking for and being able to tweak, say, a funnel report or, you know, territory goal report, maybe you're not as familiar with how to add a literal into a report and do a percent.

Field, but you can take a pre-made report and make those adjustments. This is a really great way to be able to pull that in.

Small asterisk that we'll get to later on, but without having to map to system field and kind of start from scratch, right? We could always briefcase those reports in, but depending on what information we were using, a lot of those were custom system fields, right? We're probably using lots of entry terms, lots of student types, those sorts of things. So the shell would be there, but it would say that that part was missing. Now, with suitcase functionality, that process becomes a lot more streamlined to pull in reports or anything else that uses custom.

Add system fields.

Reader portals. Or really lots of types of portals, but to be able to move, say, a reader portal from your undergrad instance to your graduate instance and keep that same for loop that's going through test scores, or keep the formatting the same. Or maybe we have a couple of different workflows within the same instance that we want to tweak that.

Portal. For that, we would want to save it as a copy, but keep some of that dynamic content to be able to move those as entire packages. And not having to start from scratch makes a huge difference in consistency and efficiency. And once again, as Megan mentioned, to be able to collaborate right if folks are willing to share these suitcase ID's, to be able to have a starting point for these gets you really far.

Dashboards. I love dashboards and being able to make some really cool logic on dashboards with sometimes pretty complicated liquid markup or subquery exports in the background. So the GIF here is walking through specifically showing gender identity in an inclusive way so students are able to say other for their gender identity. And there's quite a bit of logic on the back end to show it in a friendly way to the counselor that would be going to that.

Students record so they are informed of what that student's gender identity or identities would be. So because it's a multi value field, obviously getting to that data can be a little bit.

If he and or not clean, so we're just kind of cleaning it up on the back end. Now I will say this could also just be a query library export, but once again as we mentioned previously, you can also suitcase query library exports. So that could certainly be something that the slate community would share as well.

Or just a pretty starting point for a dashboard to be able to suitcase it in.

Query libraries. Have you counted how many times I've said it yet in this webinar? It's like my favorite new thing in Slate. Being able to pull these in is so huge, not having to understand all of the INS and outs. This is a screenshot from one of the suitcase ID's that technicians put together that you can bring into your instance. We do have links at the bottom of the slides that we'll share later, so if you want to reference these articles, they have the suitcase IDs in them. You'll see there's a ton. This isn't even the full list.

Within this query library of pre building things that were previously in the Slate Template library, but because it's in the query library, you don't need to know custom SQL to get to it. You can tweak those in the places that you're using them without affecting the kind of template version of those within the query libraries.

And I think that's our last use case and I'm curious and your answer can't be query libraries. Which do you think you're most excited about which? Which innovative use case would you would you recommend starting with like tomorrow?

Maintaining form logic just saves so much time, so I would say either forms or obviously events or or scheduler.

Yeah.

Awesome.

Now let's get into some tips. So some pieces to keep in mind once you've enabled suitcase, or maybe to keep in mind before you decide to kind of go down that one way path and enable suitcase.

Because there is the incompatibility between briefcase and suitcase, we want to make sure that you're still able to get two things that you may have been using that briefcase ID for. So, for example, say I'm in an instance that we've already enabled suitcase in.

I find a knowledge base article where there's a helpful briefcase ID. I cannot bring that briefcase ID into my suitcase. They are completely incompatible with each other. So if I see a suitcase ID and then knowledge base article, and I haven't enabled Suitcase, I also can't bring it in. So before you've enabled suitcase, if there are any objects that you would want to be able to move, making sure that you have those in your instance so once you have them in your.

If you changed suitcase, you can always create the suitcase ID, but because they they don't work with each other, we want to make sure you're not losing the ability to to bring those objects in.

I mentioned kind of having an asterisk with some of the functionality. System field mapping is not completely consistent yet in suitcase, so hence our last bullet on this slide. Double check everything as you're bringing things in. This is still absolutely a new feature that is in the works. Even as we were kind of doing research and testing things, we saw functionality change and improve as we were putting together functionality. So for the record, September 27th.

Things may change in the future in terms of functionality, but as of right now make sure that if you are kind of following the suitcase tabs and changing which of those custom system fields that it's mapped to. So for example, if I'm bringing in that funnel report and it's mapping to entry term.

Your entry term is a custom field, so that's going to be mapped to a different custom field. You'll pull your custom field from the drop down double check that it did in fact map to your system field correctly. The fastest way to do this is to go into if you're in a form, show form logic and you'll be able to see what everything is mapped to without having to double click into all of them.

Prompt conditions do not yet copy over into suitcase. You'll get that like placeholder, you know this this object has disappeared. Kind of red error message that is forthcoming. So when you go into suitcase and you create objects to pull them over, the prompt logic is a part of those kind of checklist items where you can selectively bring things into the suitcase or not. That's there. It's intended suitcase functionality that's just forthcoming. So definitely keep an eye out for when prompt conditions are going to pull over.

However, I will say because we now have configurable joins in prompt conditions, it is at least easier to be able to pull kind of those prebuilt filters into prompt conditions even without them copying over with suitcase.

We mentioned this one earlier, but just keep in mind that you have more options within that suitcase module to add things into the suitcase than within the item itself. So App logic is kind of my go to example of. When you're within app logic, you can't add it to a suitcase, but you can within the suitcase interface itself.

One thing that we stumbled into, it does not appear currently that you have the ability to copy a form into an event template or a scheduler template when suitcase is enabled. Hopefully that is something that is not always going to be the case, but previously when when you didn't have suitcase enabled, if you went to copy form you had that drop down and you could either do form or event template or scheduler template. That is no longer an option within suitcase so just keep that in mind and.

Other thing to kind of consider as you are choosing to enable suitcase or not.

As always, when you bring things over, double check everything. Make sure your form logic is working, make sure all the fields are mapped properly. We do want to obviously thoroughly test things once we bring them in, but it should save you quite a bit of work in terms of getting it set up.

What can't be suitcase? This is not an exhaustive list, but these are kind of the things that came to our mind that we wanted to see if we could suitcase them.

Query bases cannot be suitcases. We wanted to throw in a use case for all of these just so you had contacts as so why would you want to suitcase any of these things?

For those who are not aware, there is a person document export query base and a couple of exports and filters I think within showcase within the admissions showcase module. So that was one that we thought if we could just package all of those things together, suitcase them in, that would be a great way to add a person scope document export functionality to instances. That is not currently something that can be suitcase. It's not very time consuming to recreate that query based from from showcase though.

Fields.

This one's pretty easy to download fields and re upload them via upload data set. However, our thought was can you suitcase an entire data set? Could we create a data set with fields, forms, rules, all of those sorts of things just in one suitcase package that is not currently possible.

Person records. I don't know if we were to have a big use case for this, but sometimes you built out a really great test record. Maybe test gets wiped or you know, whatever. It might be that you would want to move a person over that's not currently suitable.

Rules just given the complexity of rules and this is not something that can be suitcase used. So this would be a great great use case of really testing things out, things out in the test environment and then wanting to build them into production. That is something you would still have to rebuild in the production environment.

Workflows is not currently. You can't bring the whole workflow into a suitcase and move it into say another environment.

Content blocks are another thing that cannot be suitcase. I'll be honest, my main reason for wondering if they could be was that you can't upload them via upload data set. So that maybe there would be a workaround to try to get content blocks shared a little bit more easily potentially between like an admissions and a student success instance, but that's not current functionality.

What's coming for the future in suitcase? One of the kind of smaller things that will be rolled out with suitcase in the future is searching for your suitcases. I'm not sure that anyone has pages and pages and pages of suitcases quite yet, but if you go into the suitcase and you search, it doesn't actually search for the title of the the suitcase itself. That is forthcoming functionality.

Also when you go to add a form, being able to kind of filter or search by the template or the folder of the form. Obviously we've all had folder structure drilled into us for our forum so to be able to more easily find those forms.

What's coming in the future, both kind of across the board and something that we would recommend that you do, is transitioning from briefcase IDs to suitcase IDs.

Because you are not able to use suitcase or use briefcase once suitcase is enabled.

We will slowly start to see obviously more and more suitcase ideas, but there is kind of this transition period of incompatibility and I know Megan spoke to kind of using your test environment as your briefcase world and your production environment as your suitcase world. Only sustainable for so long. We're going to have to refresh test at some point, so just know that that transition is coming over to suitcase ID's.

And then, as we mentioned, prompt conditions copying over is a forthcoming piece of functionality for suitcase.

They got muted again. All right. I'm sure we could all listen to Emma talk about suitcase and really any slate future for a lot longer. But as we near the end of our time today, we do want to provide you with a few resources to supplement today's conversation.

Emma, what's the first one?

So we wanted to throw out an example suitcase ID for you all. And the great thing about a suitcase ID is we can always add more stuff in there and you'd still be able to use that suitcase ID. No, it's not a live link, you'd have to re bring in that suitcase ID. But it's got an example mailing of an internal notification for any deliver mailings that are ending in the next two weeks. So while I'm a huge fan of using stop dates so that we have that refresh.

We know that messages aren't just going on forever and ever that we haven't kind of reevaluated each year. It's also sometimes kind of easy to forget the messages that have stopped because they aren't on your radar. So I like to have that internal notification of, hey, these messages are ending within the next couple of weeks, should they stay off or should we be updating them and then rescheduling them for that next cycle?

There are also some cool things coming in the future with kind of crowdfunding those suitcase ID's. So community forums are going to be a great place to be able to share those suitcase ID's to ask questions about ones that technicians has provided or for example, like the ones that we've created that others have created. There is a lot more opportunity for collaboration.

Great. Thanks, Emma. Of course, we can't plug knowledge base, documentation, forums, social channels enough. We'll be providing the PDF of the slides. I think there are some notes in the chat about not necessarily being able to see all the screenshots and things, so we will be providing those and you'll be able to have those links as well to the suitcase article first. This is updated in late August. The suitcase is rolling out into our environments. Also, if webinars are your thing, feel free to hang out with me and I for just a little bit longer as our stump the Slate Squad webinar begins in just half an hour or so.

And while I'm sure you would love to spend that extra hour with us, we get that you may not have planned to do so. So feel free to register for the webinar just to make sure you're set the recording. I will put that link in the chat in just a moment. If you are free and are trying to decide whether or not to come, the entire webinar will be Q&A, where the panelists will field questions from registrants and the live audience, all working to stump our slate squad. And finally, if you're ready to chat about your next slate optimization, marketing, or enrollment project, let's connect.

Nita, I think we have plenty of time here for some questions.

Great. So we had a ton of questions come through the chat as well as when folks registered. So what I'm going to do is I'm just going to read off the relevant suitcase related questions. Anything that we've found may not have been relevant to suitcase we are going to leave off at this time just so that you guys can reach out to Megan and Emma directly and have those questions answered. Just for the sake of time, we'll go through the ones that are relevant. Before I do start, I was chatting with our suitcase. Well the engineer who has worked.

On the feature for suitcase and that prompt conditions, one that we were discussing has actually been fixed in our last push, so that one is good to go.

And then.

So we're already we're already outdated, Nida. We haven't even finished the webinar.

Yeah.

Alright, great. And then I also know that he did mention that in the future, which is something coming down the line, you will be able to take those briefcase ID's and get those into suitcase. So just keep an eye out for that one as well.

Wow, that's great news.

Awesome.

So I will start with the questions that came through at the time of registration. So the very first question was that that briefcase has been helpful in a lot of instances, but it came with some limitations and there are some things that simply aren't available to briefcase and must be built in the live environment. What will be similarly unavailable in suitcase, which I think you guys briefly touched on some of those.

Yeah, I can pull that slide back up again just so we can get a good list of that. I'd be curious if there are specific things that are not listed here that you'd want to suitcase that we didn't touch on, but this might be a good list to start with.

The second question was very specific into how to use step by step using suitcase for different situations queries, reporting portals, which I think you guys touched on. So for that one I would say just reach out to you guys and bring your unique case.

Alright.

Absolutely.

Perfect.

Right. And then we had one where someone said that they used suitcase to move projects from test to production and vice versa. They just wanted to know how to use the report part suitcase option since they have successfully pulled in some report parts, but they cannot seem to figure out how to move them to a newer existing report.

To move a report from test into a report that already exists in production, like like, merge them.

It's not clear, but that's what I'm gaining from this.

Yeah.

OK. So yeah, it would just be moving the item in. It wouldn't be merging existing items. You could certainly move it from test to production and then kind of decide which way is the best way, right, to to recreate into that report or to pull the other or keep them separate. But yeah, suitcase wouldn't affect being able to combine them.

Act.

OK. And then someone was wondering if they can use suitcase to update forms for their new cycle in the batch.

Suitcases is copying and pasting so.

I'm trying to think of a way that that would impact updating with cycle prep.

I was gonna say unless your plan is to archive last years and you just want to like preserve the data from last year and copy and paste in and then update afterwards. I kind of I was thinking of that when we were talking about the deliver mailings. I would highly recommend doing that as a part of your cycle prep because it's the same concept you're. You know, we recommend archiving all of your communications and then tweaking with new UTM codes or new dates content, whatever that looks like.

So that would be much quicker, and I think you could do the same with forms if that's your approach. We'd maybe want to talk about whether it makes sense to to start over for cycle prep with forms, but it might be something to consider.

One comes through the chat a few times. They just want clarification that enabling suitcase overrides briefcase and makes briefcase not usable.

Yes, until the new.

Increased compatibility with being able to use briefcase IDs with suitcase. But yes, once you enable suitcase, you cannot create a new briefcase ID. Once the new functionality that Nita just mentioned happens, it sounds like you'll be able to bring in a briefcase ID, but you wouldn't be able to create a new briefcase ID. So say you were trying to share a report with a colleague at another institution that has not enabled suitcase. They only have briefcase.

You have suitcase enabled. Unless you already have that briefcase ID created, you would only be able to create a suitcase ID which is incompatible with their instance.

So it may be worth hanging tight if you have a ton of briefcase needs until need is update goes through into production. Unless need it, we're suggesting that that is through already or it's coming.

It is coming.

Perfect. So, yeah, I'd hang tight for that.

Alright, perfect. We had one that talks about CJ's, so briefcase tends to not work well with CJ's and so they were wondering if particularly particularly with the aliases for any join tables to suitcase remedy this.

I would hold until the system fields are coming over more consistently. In my mind those those fixes go hand in hand with each other to be able to have those custom tables. Those custom fields be coming over correctly, so I think I would hold until the updates with with system fields copying over more consistently.

Perfect. Next question was can suitcase move a complex standalone query into a report?

Into a report. I don't think it affects that functionality. That is not something I tested specifically.

All right. Next was where can we get the GPA calculator? We saw that one come through a few times.

That that one was a technicians one that is listed. Let me find the link and I'll throw it in the chat. Um, and there's instructions at the top of it as well. I'm giving credit where credit is due from where it started from.

So let me put that in the chat for you.

And I think there's actually a few in this article, if I remember correctly.

Perfect that one in the chat.

Create.

OK, OK. And then some folks had reached out about that resource temporarily unavailable error that we were receiving. That bug is still being worked on. So as soon as we have an update out there, you'll see that come through in the forums so that one we can move forward.

Then it was again. One suitcase is turned on his briefcase and activated, which we've touched on.

And let's see. And then we had do fields get overwritten with suitcase? So for example if we already have a field that is set up for our needs and then suitcases brought in that uses the same name field with different default or prompts tied to it, does it create a separate field with the same name or like name, under score 2 so it leaves the original alone?

That's a great question because in all of our testing it kind of ignored changing the system field. I don't know that I can speak to that because when we would update that fields tab within suitcase, it would just remain as the original 1. So it it didn't successfully create that second field. So I have not been able to test that yet.

And then we received that question about putting that ID in the chat, which I saw you did. And our last question came in from Jason, which was over half the report to my slate showcase aren't available for our show showcase. The ones that aren't have to be briefcase, why are some available in some not?

So within showcase some some you can briefcase and some you can suitcase.

Is the question perhaps.

Yes.

Not entirely sure. Let's see.

I don't have to look in showcase and see the specific example. Everything that I've seen is instance wide. So you can either copy the briefcase or you can copy to suitcase. I've never seen both within the same instance right? Since we've talked about really that mutually exclusive kind of Early access feature. Showcase obviously could be set up differently given that it is, you know, a special environment. So I'd have to take a look at that and and see. Maybe it's based off of when the report.

Was created versus kind of that overall setting of the instance.

Perfect. And those are all of our questions on suitcase.

Awesome. Well, if you have any other questions about suitcase or anything else we talked about, we will be sharing the slides that you can see in more detail and get the links and all of that good stuff. But please feel free to reach out to us. We love talking about slate stuff, so let us know what questions you have.

Definitely.

Thank you everyone.

Thanks everyone.